Date: Fri, 30 Oct 1998 18:44:25 -0500 From: Dennis <dennis@etinc.com> To: Archie Cobbs <archie@whistle.com> Cc: hackers@FreeBSD.ORG Subject: Re: scanf in the kernel? Message-ID: <199810301830.SAA28485@etinc.com> In-Reply-To: <199810302100.NAA18888@bubba.whistle.com> References: <199810301814.KAA16349@bubba.whistle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
At 01:00 PM 10/30/98 -0800, you wrote: >Archie Cobbs writes: >> > Just wondering what the general feeling would be about having scanf in >> > the kernel? As we move towards more abstract representations of things >> > (eg. device names), it's becoming more important to be able to parse >> > strings inside the kernel. >> > >> > Doing this in hand-rolled code is tedious, error-prone and results in >> > code that can be hard to read and maintain (as everyone does it their >> > own way). >> > >> > If this isn't totally repulsive, I'll roll a somewhat smaller version >> > of the libc vfscanf for general approval. > >Also- >Seems like the kernel was missing memmove(), memcpy(), and/or memset() >at some point. I like using these better than bcopy()/bzero() because >they are more ANSI and portable... #define memcpy(d,s,n) bcopy(s,d,n) not exactly rocket science :-) sscanf..you lazy bastard....although I am pleased as punch that printf now supports leading zeros...when did that happen? db Emerging Technologies, Inc. http://www.etinc.com ISA and PCI T1/V35/HSSI Cards for FreeBSD, LINUX and BSD/OS Bandwidth Manager http://www.etinc.com/bwmgr.htm To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199810301830.SAA28485>