From owner-freebsd-hackers  Fri May 11 23:35:36 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from guild.plethora.net (guild.plethora.net [205.166.146.8])
	by hub.freebsd.org (Postfix) with ESMTP id E38FB37B423
	for <freebsd-hackers@freebsd.org>; Fri, 11 May 2001 23:35:33 -0700 (PDT)
	(envelope-from seebs@guild.plethora.net)
Received: from guild.plethora.net (seebs@localhost.plethora.net [127.0.0.1])
	by guild.plethora.net (8.10.1/8.10.1) with ESMTP id f4C6ZUq15722;
	Sat, 12 May 2001 01:35:30 -0500 (CDT)
Message-Id: <200105120635.f4C6ZUq15722@guild.plethora.net>
From: seebs@bsdi.com (Peter Seebach)
Reply-To: seebs@bsdi.com (Peter Seebach)
To: dan@bsdpro.com
Cc: freebsd-hackers@freebsd.org
Subject: Re: adding a new function to libc 
In-reply-to: Your message of "Sat, 12 May 2001 02:10:45 EDT."
             <01051202104500.95296@blackhole.BSDpro.com> 
Date: Sat, 12 May 2001 01:35:29 -0500
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <01051202104500.95296@blackhole.BSDpro.com>, Daniel Hemmerich writes
:
>Any comments, suggestions, swears concerning adding a new function, 
>strndup(), to libc?

Well, the obvious potential concern is that str[a-z]* is reserved namespace,
and what if a future spec has a *different* strndup?

>So that instead of permitting it to attempt to allocate a large chunk of 
>memory, it is possible to give it a max length.

Well, this one is clearly wrong, because if you have a string of max_len,
it isn't terminated.

-s

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message