Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Posted-Date: Mon, 16 Oct 2000 15:02:33 -0500 (CDT) Reply-To: From: "Gary R. Van Sickle" To: "'DJ Delorie'" , Subject: RE: RFC: linux compatibility Date: Mon, 16 Oct 2000 15:02:27 -0500 Message-ID: <001201c037ac$026e2790$1d01a8c0@BRAEMARINC.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <200010161706.NAA11350@envy.delorie.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal > > What are the existing applications expecting? > > timezone in cygwin1.dll is "char *timezone();" > > timezone in linux is "extern int timezone;" > Sounds like the Cygwin way is better. POSIX must have something to say on this particular issue, no? > > 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? Is the global variable way the new definition? I'm not sure we'd want to migrate to it. But #defining it makes it easy to do both. > And that *all* applications that use "timezone" *must* > include one of our headers, I'm assuming 'extern int timezone' is in a standard header somewhere. Is this not the case? > even though plenty of existing sources > *assume* "extern int timezone;" without including any headers? Then those apps are broken and should be fixed to include whatever header this global variable is defined in. Gary R. Van Sickle (tiberius AT braemarinc DOT com) Braemar Inc. 11481 Rupp Dr. Burnsville, MN 55337 -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com