Re: perennity of cygwin_internal(CW_GET_ERRNO_FROM_WINERROR,err)

2005-08-26 Thread Corinna Vinschen
On Aug 26 11:13, Samuel Thibault wrote: > Corinna Vinschen, le Fri 26 Aug 2005 11:05:21 +0200, a écrit : > > On Aug 26 00:43, Samuel Thibault wrote: > > > While writing a library for instance, we'd like > > > to return appropriate errno values, and for this > > > cygwin_internal(CW_GET_ERRNO_FROM_W

Re: perennity of cygwin_internal(CW_GET_ERRNO_FROM_WINERROR,err)

2005-08-26 Thread Samuel Thibault
Corinna Vinschen, le Fri 26 Aug 2005 11:05:21 +0200, a écrit : > On Aug 26 00:43, Samuel Thibault wrote: > > While writing a library for instance, we'd like > > to return appropriate errno values, and for this > > cygwin_internal(CW_GET_ERRNO_FROM_WINERROR,err) would be much useful. > > > > Docume

Re: perennity of cygwin_internal(CW_GET_ERRNO_FROM_WINERROR,err)

2005-08-26 Thread Corinna Vinschen
On Aug 26 00:43, Samuel Thibault wrote: > Hi, > > While writing a library for instance, we'd like > to return appropriate errno values, and for this > cygwin_internal(CW_GET_ERRNO_FROM_WINERROR,err) would be much useful. > > Documentation says "Stay away unless you know what you're doing". Could

perennity of cygwin_internal(CW_GET_ERRNO_FROM_WINERROR,err)

2005-08-25 Thread Samuel Thibault
Hi, While writing a library for instance, we'd like to return appropriate errno values, and for this cygwin_internal(CW_GET_ERRNO_FROM_WINERROR,err) would be much useful. Documentation says "Stay away unless you know what you're doing". Could it be removed some day, and hence we shouldn't use it?