Date: Wed, 7 May 2003 15:41:55 +0200 (CEST) From: Harti Brandt <brandt@fokus.fraunhofer.de> To: Christoph Hellwig <hch@infradead.org> Cc: freebsd-arch@FreeBSD.org Subject: Re: `Hiding' libc symbols Message-ID: <20030507154105.A3282@beagle.fokus.fraunhofer.de> In-Reply-To: <20030507143611.A23293@infradead.org> References: <20030501182820.GA53641@madman.celabo.org> <20030505110601.H53365@beagle.fokus.fraunhofer.de> <3EB7CC73.9C61C27E@mindspring.com> <20030506152605.GE77708@madman.celabo.org> <20030506162352.GC78486@madman.celabo.org> <20030507143611.A23293@infradead.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 7 May 2003, Christoph Hellwig wrote:
CH>On Wed, May 07, 2003 at 02:32:40AM -0700, David Schultz wrote:
CH>> > strlcpy(struct string *a, struct string *b)
CH>> > {
CH>> > if (a->size == 0) {
CH>> > b->size = 0;
CH>> > return;
CH>> > }
CH>> > /* really copy the string */
CH>> > }
CH>>
CH>> Hmm...but that program is broken. If someone overrides a symbol
CH>> reserved by the C standard, he deserves whatever he gets. It is
CH>> not unreasonable to expect applications to avoid using reserved
CH>> symbols for thier own purposes.
CH>
CH>strlcpy is not in any standard..
It is in ANSI's standard namespace...
harti
--
harti brandt,
http://www.fokus.fraunhofer.de/research/cc/cats/employees/hartmut.brandt/private
brandt@fokus.fraunhofer.de, harti@freebsd.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030507154105.A3282>