bug-m4
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: address@hidden: Re: CVS commit: pkgsrc/devel/m4]


From: Joerg Sonnenberger
Subject: Re: address@hidden: Re: CVS commit: pkgsrc/devel/m4]
Date: Wed, 25 Jul 2007 12:49:57 +0200
User-agent: Mutt/1.5.13 (2006-08-11)

[I'm sorry that the original mail was a bit aggressive, but finding out
why a working implementation of a function is replaced in the maze of
autoconf macros is not a good base for nice chatting].

On Tue, Jul 24, 2007 at 01:44:31PM -0600, Eric Blake wrote:
> GNU M4 relies on POSIX behavior in the stdio library in order to comply
> with POSIX requirements on its own behavior.

This is a noble goal and worth supporting.

  True, GNU M4 does not yet
> fully comply with POSIX, but I am working on enhancing it to do so.  If
> you are unwilling to fix NetBSD's fflush to comply with POSIX, then you
> should not complain that gnulib is doing the job on your behalf.

To quote SUSv3:

If stream points to an output stream or an update stream...
If stream is a null pointer, ...

Using it on an input stream doesn't seem to be POSIX at all. This seems
to be in line with the historic behaviour since C89, but I can't check
that due to lack of the standard document.

> If gnulib's approach does not work on DragonFly, you are welcome to patch
> either DragonFly to comply with POSIX, or submit a patch to gnulib so that
> gnulib's approach will work on DragonFly.

I'm not even sure what gnulib tries to achieve here and I'm certainly
opposing its use of stdio internals. It seems that the existing fpurge
interface *might* be what is desired here, but I am not sure.

Joerg




reply via email to

[Prev in Thread] Current Thread [Next in Thread]