Re: [Quickfix-developers] UtcTimeStamp::tm_isdst = -1

[Oren M. <or...@qu...>]

It's because of how we are doing time comparisons in some places.  The 
problem is when you need to do conversions to time_t using mktime.  If 
you are in a time zone that is observing daylight savings, and you do a 
mktime, if you convert back into a tm_struct you will be one hour off.  
By setting this value to -1, the system will do the appropriate check 
for the timezone when doing the conversion.  Why are we using time_t?  
Mostly to make it easier to do time comparisons.  I don't think it is 
really justifiable to keep doing this.  If we get rid of using time_t 
and rewrite the UtcTimeStamp comparison operators to use the 
constituents of the tm struct, we can probably stop doing this.

--oren

On Aug 2, 2004, at 1:46 PM, Brendan B. Boerner wrote:

> QuickFIX Documentation: 
> http://www.quickfixengine.org/quickfix/doc/html/index.html
> QuickFIX FAQ: http://www.quickfixengine.org/quickfix/doc/html/FAQ.html
> QuickFIX Support: http://www.quickfixengine.org/services.html
>
> Hi,
>
> UtcTimeStamp::setCurrent() sets tm_isdst = -1, why is this done
> instead of using the value as set by gmtime()?
>
> Thanks,
> Brendan
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by OSTG. Have you noticed the changes on
> Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
> one more big change to announce. We are now OSTG- Open Source 
> Technology
> Group. Come see the changes on the new OSTG site. www.ostg.com
> _______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers
>