Mail Archives: djgpp-workers/2000/06/29/02:59:38
On Wed, 28 Jun 2000, Laurynas Biveinis wrote:
> Eli Zaretskii wrote:
> > Yes. But this doesn't fix the tempnam problem, does it?
>
> Hm? The following part of that patch doesn't?
>
> Index: djgpp/src/libc/compat/stdio/tempnam.c
> ===================================================================
> RCS file: /cvs/djgpp/djgpp/src/libc/compat/stdio/tempnam.c,v
> retrieving revision 1.2
> diff -u -r1.2 tempnam.c
> --- tempnam.c 1997/10/28 19:22:12 1.2
> +++ tempnam.c 2000/06/28 08:31:01
> @@ -1,5 +1,7 @@
> +/* Copyright (C) 2000 DJ Delorie, see COPYING.DJ for details */
> /* Copyright (C) 1997 DJ Delorie, see COPYING.DJ for details */
> /* Copyright (C) 1995 DJ Delorie, see COPYING.DJ for details */
> +#include <libc/stubs.h>
Sorry, I missed the patch to tempnam.c (I only remember seeing the
patch for fsext.c).
> > I don't think this is a test. It is no more a test than the fact that we
> > use a lot of -W* switches, to reveal possible bugs. I think that
> > polluting ANSI/Posix namespace is a grave problem, and if an automated
> > tool finds quite a few problems, even after several cleanup efforts, it's
> > a clear sign that manual procedures are inadequate.
>
> I wonder if anyone has reported this grave problem in 2.03 ;-)
I don't remember any such reports, and I didn't know about
libclink/check until DJ mentioned it in this thread. So I never ran
that utility during v2.03 development. All the stubs-related cleanups
were a result of manual inspection.
- Raw text -