Re: Bison-1.28 No Error Bug

[Hans Aberg]

At 10.38 +0200 0-10-04, Akim Demaille wrote:
>Hans> For the port, I want as few as possible, because it's easier to
>Hans> ... In order to prevent
>Hans> mistakes with f(...)  arguments, one can first define the single
>Hans> warn() above, and then all the other warnx wrapping around it.
>
>We must have misunderstood each other.  Warn, warni, warns etc. are
>dead,

No I think understood; but some do not like the (...) constructs, as there
is not compile or runtime check for type correctness. One idea of C++ name
overloading was to get rid of the need for that (...). -- But that is
another discussion :-); I don't really care myself.

>but now there is
>
>/* Informative messages, but we proceed. */
>
>extern void warn (const char *format, ...)
>     __attribute__ ((__format__ (__printf__, 1, 2)));
...

(Note that names starting with _ are in ISO C/C++ reserved for the
implementation of the C/C++ compiler, and in C++ that is also true for
names containing __. -- Speaking about about ISO C/C++, I hope you know
that these can now be bought for "just" $18 each online from ANSI; the
identical ISO, non-ANSI C++ standard costs $245.)

>If you find a means to factor this without cluttering bison's sources,
>then fine, but clarity, simplicity and maintainability of the sources
>of Bison are more important for us than interfacing with IDEs :(

I would need to pick down the latest sources and check how well it works
when integrating that with my stuff. -- Right now, what holds me back, is
that I have not been able to figure out a convenient way of taking the
sources down from your CVS. -- If you have some recent sources and can send
them to me as .tgz mail attachment, I can try (but send as little as
possible though, just what's in "src", because I pick it down using a slow
56 kbaud modem).

  Hans Aberg