From owner-freebsd-current Wed Nov 3 10:57:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 70598154AE for ; Wed, 3 Nov 1999 10:57:19 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id TAA32338 for ; Wed, 3 Nov 1999 19:57:04 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org Subject: YAJKHT (Yet a Junior kernel hacker task) In-reply-to: Your message of "Wed, 03 Nov 1999 09:54:27 PST." <199911031754.JAA67357@freefall.freebsd.org> Date: Wed, 03 Nov 1999 19:57:03 +0100 Message-ID: <32336.941655423@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Now that we have grudingly accepted the existence of the ctype macros (isdigit(3) and friends) along with strto{u}[ql](3) into the kernel, there are a considerable number of places where they could be used to make code more readable. Needless to say you need to *test* your patches before you send them to us with send-pr. About the only place which is sacred is the gdb-stubs, please be aware that particular isolation requirements apply to that code which make it un-smart to rely on library functions. (that is why the gdb-stubs even come with their own strlen(3) & strcat(3) -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message