> > 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 ([EMAIL PROTECTED])
Braemar Inc.
11481 Rupp Dr.
Burnsville, MN 55337
--
Want to unsubscribe from this list?
Send a message to [EMAIL PROTECTED]
