This is the mail archive of the java-discuss@sourceware.cygnus.com mailing list for the Java project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: Integrating Win32 changes

To: Jeff Sturm <jsturm at sigma6 dot com>
Subject: Re: Integrating Win32 changes
From: Tom Tromey <tromey at cygnus dot com>
Date: Mon, 17 Jan 2000 14:47:41 -0800 (PST)
Cc: Per Bothner <per at bothner dot com>, java-discuss at sourceware dot cygnus dot com
References: <00a201bf612c$34204a90$010010ac@brookfield.net><388390F3.29001C12@sigma6.com><m2puv09xib.fsf@magnus.bothner.com><38839CE8.DF5D6A20@sigma6.com>

>>>>> "Jeff" == Jeff Sturm <jsturm@sigma6.com> writes:

Jeff> One could argue that WIN32 is a "feature" too, meaning the Win32
Jeff> API is available.

I see Windows as a family of features.  I don't think we need to have
a new macro for each member of the family, until we get to the point
where we need to conditionally compile depending on the target family
member (e.g., some API implemented on NT but not on WinCE).

Jeff> #if defined(WIN32) && !defined(__CYGWIN32__)
Jeff> ...
Jeff> #endif

This is a bit gross.  We could just introduce our own "Windows family"
macro and set it from configure.in as appropriate.

Tom

References:
- Integrating Win32 changes
  - From: Jon Beniston
- Re: Integrating Win32 changes
  - From: Jeff Sturm
- Re: Integrating Win32 changes
  - From: Per Bothner
- Re: Integrating Win32 changes
  - From: Jeff Sturm

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]