On Sat, Jun 26, 2004 at 01:09:40PM -0400, Christopher Faylor wrote: > On Sat, Jun 26, 2004 at 12:05:54PM -0400, Pierre A. Humblet wrote: > >Beware, I found this: > >2000-05-19 DJ Delorie <[EMAIL PROTECTED]> > > * libc/include/stdio.h: no getc/putc macros for cygwin; causes > > compatibility issues with different dll versions > >so you may need to recompile when updating cygwin. > > Also wouldn't that work around the file locks that were ostensibly put > there for a reason?
That crossed my mind. But there is no file lock in the macro, which is used by systems other than cygwin. How do they manage it? I also assume that single threaded programs don't need the lock. I would be perfectly happy to have a thread-unsafe getc/putc macro, and to use fgetc/fputc when I care about multithreading. Digging deeper, I see there is a function getc_unlocked. Using it instead of getc improves the speed by a factor 5. Now that I know about it, I will redefine getc to getc_unlocked when porting single threaded applications. That issue may be a factor in the legendary slowness of Cygwin. Pierre -- 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/
