On Thu, Apr 21, 2005 at 07:24:00PM +0100, Dave Korn wrote: >----Original Message---- >>From: Christopher Faylor >>Sent: 21 April 2005 19:20 > >>On Thu, Apr 21, 2005 at 05:39:57PM +0000, Eric Blake wrote: >>>Also, I've noticed that some cygwin syscalls are sloppy, and change >>>errno to EISDIR even when they are successful. >> >>Cygwin does try only to set errno when there is an error. If you have >>specific evidence to the contrary please report it. > >In any case, it's legitimate to set errno to anything you like in a >system call, because the application is only allowed to pay attention >to the value of errno if the system call returns an error exception. >If the system call returns success (generally zero), the value of errno >is undefined and it's not valid to pay any attention to it.
Yes. I know. Nevertheless, Cygwin does try only to set errno when there is an error. There are some cases where that isn't true but I didn't see any that referred to EISDIR. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
