Date: Tue, 14 Aug 2001 15:28:36 +0300 From: "Eli Zaretskii" Sender: halo1 AT zahav DOT net DOT il To: acottrel AT ihug DOT com DOT au Message-Id: <2593-Tue14Aug2001152836+0300-eliz@is.elta.co.il> X-Mailer: Emacs 20.6 (via feedmail 8.3.emacs20_6 I) and Blat ver 1.8.9 CC: pavenis AT lanet DOT lv, djgpp-workers AT delorie DOT com, sandmann AT clio DOT rice DOT edu In-reply-to: <007201c124aa$37717ff0$0a02a8c0@acceleron> (acottrel@ihug.com.au) Subject: Re: Windows 2000 patch for utime.c References: <3B7909ED DOT 32020 DOT 19CCE6 AT localhost> (pavenis AT lanet DOT lv) <3B791B0C DOT 22177 DOT 5CB07E AT localhost> <007201c124aa$37717ff0$0a02a8c0 AT acceleron> Reply-To: djgpp-workers AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp-workers AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > From: "Andrew Cottrell" > Date: Tue, 14 Aug 2001 20:16:41 +1000 > > Instead of re-inventing the wheel Allegro has support for a number of > different OS's and it tests for these and sets an appropriate variable and > you get to the variable via a function call if I remeber correctly. It may > be usefull to look at this to see how this works as Allegro now works on > DJGPP, VC++, GNU on Linux and looks like some other platforms as well. IIRC, Allegro does the same, but in addition it looks at some environment variables normally set on NT and its family. I don't think the library should look at those environment variables unless it absolutely has to, because environment variables is something a user can set and reset.