Bruno Haible <[EMAIL PROTECTED]> writes:
> I would actually prefer to have this in the autoconf manual, side-by-side
> to the "Shellology" chapter, because
> - gnulib so far doesn't provide a "make install" that would install a
> gnulib.info documentation file.
> - Nearby to "Shellology",
Paul Eggert wrote:
> But glibc asctime does not have the problem, since it never has
> undefined behavior. The glibc manual isn't really intended to be a
> manual for porting code to non-glibc systems
OK, then the Linux manual pages are not the right place either.
> Perhaps we could add a portab
Bruno Haible <[EMAIL PROTECTED]> writes:
> OK, so where is the list of C functions containing pitfalls?
Good question.
> If you are serious about deprecating asctime, ctime, asctime_r,
> ctime_r, I think this should be reflected in both the glibc manual
> and the Linux manpages.
But glibc ascti
Paul Eggert wrote:
> The next POSIX will allow the current Solaris behavior, along with
> worse behaviors, so I think it's better if we wash our hands of these
> functions entirely. asctime and ctime are only historical curiosities
> now, and asctime_r and ctime_r are well-intentioned mistakes.
O
