Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Date: Mon, 16 Oct 2000 13:06:31 -0400
Message-Id: <200010161706.NAA11350@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: tiberius AT braemarinc DOT com
CC: cygwin AT sourceware DOT cygnus DOT com
In-reply-to: <000a01c03791$b2fd8a80$1d01a8c0@BRAEMARINC.COM>
	(tiberius AT braemarinc DOT com)
Subject: Re: RFC: linux compatibility
References:  <000a01c03791$b2fd8a80$1d01a8c0 AT BRAEMARINC DOT COM>


> What are the existing applications expecting?

timezone in cygwin1.dll is "char *timezone();"

timezone in linux is "extern int timezone;"

> One or the other, right?  The one that isn't there yet gets the
> #define treatment.

So what you're saying is that we can *never* migrate to the new
definition?  And that *all* applications that use "timezone" *must*
include one of our headers, even though plenty of existing sources
*assume* "extern int timezone;" without including any headers?

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com