From owner-freebsd-hackers Sat Oct 31 12:04:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA09012 for freebsd-hackers-outgoing; Sat, 31 Oct 1998 12:04:32 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles325.castles.com [208.214.167.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA09005 for ; Sat, 31 Oct 1998 12:04:29 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA01039; Sat, 31 Oct 1998 12:04:07 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810312004.MAA01039@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "John C. Place" cc: hackers@freebsd.com, hackers@FreeBSD.ORG Subject: Re: scanf in the kernel? In-reply-to: Your message of "Sat, 31 Oct 1998 14:46:49 EST." <19981031144649.A278@ka3tis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 31 Oct 1998 12:04:07 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Fri, Oct 30, 1998 at 10:25:39AM -0500, Bill Fumerola wrote: > > I'm not a kernel-hacking kind of guy, but I know just from personal C > > experiences that scanf makes things a lot easier to change later on and > > easier to get a visual representation of. scanf and sprintf have become my > > friend. > > > I am not one either but I thought the *printf commands are very > expensive (to the processer) and something as low level as the kernel > would one try to avoid these??? One would generally try to avoid having them anywhere in a critical path, certainly, but they're not actually that expensive, and there's always a tradeoff between speed and maintainability. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message