Re: On recent windows fileno return -2 in case of closed stdin, stdout, stderr

2020-04-06 Thread Bruno Haible
Bastien, > > So the workaround would have to be in a 'fileno' module. > > I can but I do not know how to do. does -2 is a valid fd on windows ? On Windows as well, valid file descriptor numbers are >= 0. All return values of fileno that are < 0 can be considered as invalid. But since POSIX says

Relicence explicit_bzero to GPL2+/LGPL3 dual

2020-04-06 Thread Bastien ROUCARIES
Hi, Could be possible to relicence this module under dual GPL2+ LGPL3 licence? Code is from glibc thus LGPL2+ and it will be useful for some program like fwknop Bastien

Re: On recent windows fileno return -2 in case of closed stdin, stdout, stderr

2020-04-06 Thread Bastien ROUCARIES
On Mon, Apr 6, 2020 at 8:32 PM Bruno Haible wrote: > > Hi Bastien, > > > according to > > https://docs.microsoft.com/fr-fr/cpp/c-runtime-library/reference/fileno?view=vs-2019 > > > > If stdout or stderr is not associated with an output stream (for > > example, in a Windows application without a c

Re: On recent windows fileno return -2 in case of closed stdin, stdout, stderr

2020-04-06 Thread Bruno Haible
Hi Bastien, > according to > https://docs.microsoft.com/fr-fr/cpp/c-runtime-library/reference/fileno?view=vs-2019 > > If stdout or stderr is not associated with an output stream (for > example, in a Windows application without a console window), the file > descriptor returned is -2. In previous

On recent windows fileno return -2 in case of closed stdin, stdout, stderr

2020-04-06 Thread Bastien ROUCARIES
Hi, according to https://docs.microsoft.com/fr-fr/cpp/c-runtime-library/reference/fileno?view=vs-2019 If stdout or stderr is not associated with an output stream (for example, in a Windows application without a console window), the file descriptor returned is -2. In previous versions, the file d