Re: [PATCH] SMPP validity

On Thu, Aug 22, 2002 at 04:04:23PM +0300, Oded Arbel wrote:
> 
> > -----Original Message-----
> > From: Vibhu Mohindra [mailto:[email protected]]
> > Sent: Thursday, August 22, 2002 2:03 PM
> > To: [email protected]
> > Subject: Re: [PATCH] SMPP validity
> > 
> > 
> > If the issue is solely with locatime_r(), but using localtime() and
> > the returned struct's tm_gmtoff is alright then let's do that rather
> 
> No it's not. that was the point of my previous post. using tm_gmtoff is
> a much word portability braker then using localtime_r().

A final attempt from me for us to use the underlying OS's library :-)
Why don't we use the older global variable timezone that gets set upon
return from a localtime() or gmtime() call. Other than being globally
accessible by all threads, the only difference w.r.t. tm.tm_gmtoff is
that it doesn't take into account DST. You've mentioned that localtime()
should reflect that anyway, so we're OK on that count.

After a call to localtime(),

    printf("%ld\n", -timezone/3600);

tells me I'm +6 UTC.

Vibhu

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE9ZPfHvgqsqbNQjqcRAi7AAKCE5G1HISeH60Y+lnrP0BpCPkzLHwCfb522
+THdM07TFgP5OBwbbkrw85g=
=K4ev
-----END PGP SIGNATURE-----