Eric Blake wrote:
> vasnprintf now behaves differently on mingw depending on whether 
> you are also using sigpipe-die, and this difference is at the source code 
> level 
> (faking SIGPIPE on mingw comes with a lot of baggage)

The essential idea here is right. Just two details:

  - The feature-enabling module is 'sigpipe'. 'sigpipe-die' is used when the
    application wants a behaviour that matches neither the POSIX default
    behaviour nor the POSIX SIG_IGN behaviour. Not many programs use that.
    For 80% of the programs, the POSIX default behaviour is fine.

  - vfprintf is compiled differently, depending with module 'sigpipe' is
    present or not. vasnprintf is not, since it does not deal with streams,
    only with strings.

Bruno



Reply via email to