Re: Win32 build and WINVER

2001-11-05 Thread Richard J Cox
In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED] (James Mastros) wrote: > On Sun, Nov 04, 2001 at 01:38:58PM -0500, Dan Sugalski wrote: > > Currently, I don't want to promise back before Win98, though if Win95 > > is no different from a programming standpoint (I have no idea if it > > is) the

Re: Win32 build and WINVER

2001-11-05 Thread Dan Sugalski
At 06:27 PM 11/4/2001 -0500, James Mastros wrote: >On Sun, Nov 04, 2001 at 01:38:58PM -0500, Dan Sugalski wrote: > > Currently, I don't want to promise back before Win98, though if Win95 > is no > > different from a programming standpoint (I have no idea if it is) then > > that's fine too. Win 3.

Re: Win32 build and WINVER

2001-11-04 Thread James Mastros
On Sun, Nov 04, 2001 at 01:38:58PM -0500, Dan Sugalski wrote: > Currently, I don't want to promise back before Win98, though if Win95 is no > different from a programming standpoint (I have no idea if it is) then > that's fine too. Win 3.1 and DOS are *not* target platforms, though if > someone

Re: Win32 build and WINVER

2001-11-04 Thread Dan Sugalski
At 05:26 PM 11/4/2001 +, Richard J Cox wrote: >This of course leads to the question of what is the earliest Win32 version >that Perl6 will support? Currently, I don't want to promise back before Win98, though if Win95 is no different from a programming standpoint (I have no idea if it is) th

Win32 build and WINVER

2001-11-04 Thread Richard J Cox
Currently for a Win32 build WINVER is not being set, this leads to it being set in Windef.h (included by Windows.h) to 0x0500, or "build for Windows 2000". This is OK, until (for whatever) reason a Win2k only API is called, at which point the built exe will not run on earlier versions of Windo