From owner-freebsd-current Tue Dec 19 10:40:04 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA27479 for current-outgoing; Tue, 19 Dec 1995 10:40:04 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA27452 for ; Tue, 19 Dec 1995 10:40:01 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA15039; Tue, 19 Dec 1995 11:36:44 -0700 From: Terry Lambert Message-Id: <199512191836.LAA15039@phaeton.artisoft.com> Subject: Re: Mis-feature in -current To: nate@rocky.sri.MT.net (Nate Williams) Date: Tue, 19 Dec 1995 11:36:44 -0700 (MST) Cc: terry@lambert.org, nate@rocky.sri.MT.net, current@FreeBSD.org In-Reply-To: <199512191836.LAA27072@rocky.sri.MT.net> from "Nate Williams" at Dec 19, 95 11:36:28 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org Precedence: bulk > > Actually (not that it would seem to matter), I'm anti-string-manipulation > > in kernel code. The only places this is violated currently is in the > > path parsing code and the NFS argument code. > > We all know about that, but I'm talking about the code that exists in > -current today, not in FreeBSD 10.1. > > > How many times is strlen used, and could it maybe be recoded instead? > > Why would it need to be recoded? As it stands currently (and this will > not change for some time), the code in libkern/strlen.c is completely > adequate to do the job. I meant recoded to not use strlen. wchar_t springs to mind as a likely reason. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.