On 8/18/07, Eric Blake <[EMAIL PROTECTED]> wrote: > handler. But that is more invasive, as there are already a number of > programs using atexit(close_stdout).
As a user of these functions, if a gnulib change would produce a bug in my code unless I change it, that's likely to cause a problem. That is, I don't review every single diff to gnulib for possible imact on my software. However, rather than hold back change, I'd just prefer it if my program just started to fail to compile. That is, I'd prefer that backwards-incompatible changes cause compilation failures where possible (rather than silently wrong behaviour). James.
