[libc-alpha] Re: [libc-alpha] Re: [open-source] Re: Wish for 2002

[Andreas Schwab]

Valentin Nechayev <netch@lucky.net> writes:

|> (Cc list wasn't cut)
|> 
|>  Tue, Jan 08, 2002 at 18:42:06, kaz wrote about "Re: [libc-alpha] Re: [libc-alpha] Re: [open-source] Re: Wish for 2002": 
|> 
|> > > PA02: Assess Impact (page 121)
|> > > What all GNU/Linux most GNU applications on other OSes have in common ?
|> > > glibc 
|> > 
|> > This dependency means that once you add functions to glibc, you have to
|> > support them indefinitely. The functions in questions have poorly
|> > defined semantics. For example, I can't find anything in the BSD
|> > man pages regarding what the behavior should be of
|> > 
|> >   strlcat(buffer, buffer, sizeof buffer);
|> 
|> I can't find anything in the glibc man pages what the behavoir should be
|> of strcpy(buffer,buffer).

You cannot find it because it is undefined, by the virtue of the C
standard, which has explicit wording to make it undefined (restrict
pointers).  Does the BSD manpage make the pointer parameters of strlcat
restricted pointers?

Andreas.

-- 
Andreas Schwab             SuSE Labs                  schwab@suse.de
SuSE GmbH, Deutschhherrnstr. 15-19, D-904229 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."