Date: Wed, 7 May 2003 14:36:11 +0100 From: Christoph Hellwig <hch@infradead.org> To: "Jacques A. Vidrine" <nectar@FreeBSD.org>, Harti Brandt <brandt@fokus.fraunhofer.de>, Terry Lambert <tlambert2@mindspring.com>, freebsd-arch@FreeBSD.org Subject: Re: `Hiding' libc symbols Message-ID: <20030507143611.A23293@infradead.org> In-Reply-To: <20030507093240.GA15754@HAL9000.homeunix.com>; from das@FreeBSD.ORG on Wed, May 07, 2003 at 02:32:40AM -0700 References: <20030501182820.GA53641@madman.celabo.org> <20030505110601.H53365@beagle.fokus.fraunhofer.de> <20030506093754.B838@beagle.fokus.fraunhofer.de> <3EB7CC73.9C61C27E@mindspring.com> <20030506165850.Y601@beagle.fokus.fraunhofer.de> <20030506152605.GE77708@madman.celabo.org> <20030506175017.C631@beagle.fokus.fraunhofer.de> <20030506162352.GC78486@madman.celabo.org> <20030507093240.GA15754@HAL9000.homeunix.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, May 07, 2003 at 02:32:40AM -0700, David Schultz wrote:
> > strlcpy(struct string *a, struct string *b)
> > {
> > if (a->size == 0) {
> > b->size = 0;
> > return;
> > }
> > /* really copy the string */
> > }
>
> Hmm...but that program is broken. If someone overrides a symbol
> reserved by the C standard, he deserves whatever he gets. It is
> not unreasonable to expect applications to avoid using reserved
> symbols for thier own purposes.
strlcpy is not in any standard..
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030507143611.A23293>