Integrating Win32 changes

Sat Apr 1 00:00:00 GMT 2000

Jon Beniston wrote:
> > "#ifdef WIN32" would probably be better unless the code really depends
> > on Mingw32. That'll benefit those who may be compiling with Cygwin or
> > U/WIN, or other GCC-on-Windows environments.
>> I think its best not to mix treat ming and cygwin the same. With cygwin you
> can
> use many of the posix type functions, but you cant with ming. IMHO, building
> for cygwin would link to natFileDescriptorPosix.cc whereas a Ming build
> would map to natFileDescriptorWin32.cc, for example.

Perhaps. As Per said, we may end up with three implementations of
natFileDescriptor, for Posix, Win32 and stdio. That should cover most
platforms. Many will have two or more choices. So it could become a
configurable option, with configure automatically picking the best
overall choice for a given platform.
But now we're talking about different things... the WIN32 macro
shouldn't be needed in FileDescriptor.
--
Jeff Sturm
jsturm@sigma6.com