Using seconds in Revolution

[Sarah Reichelt]

While I haven't encountered the short & long day problem, there is a 
severe problem with the convert command if your system uses 
daylight-saving. Basically, EVERY call to the convert command, adds an 
hour to the time converted, if daylight saving is on. There are 
numerous reports in bugzilla about various date conversion problems 
(62, 816, 1124, 1162) and I am trying to get the folks at RunRev to see 
this as a critical problem.

In the meantime, I suggest you follow Mark's suggestion and use Julian 
dates instead. They allow very easy date & time arithmetic.

Mark kindly allowed me to include his Julian date functions in my 
dateTime library, which you can download from: http://www.troz.net/Rev/ 
however these functions were all written before I realized the severity 
of the problems with convert during daylight-savings times, so treat 
any that use the convert command with extreme caution.

Cheers,
Sarah
sarahr at genesearch.com.au
http://www.troz.net/Rev/

On 15 Apr 2004, at 4:11 am, SimPLsol at aol.com wrote:

> Dominique,
> You are correct.
> Yes, I'm working in California, where it is now daylight savings time.
> Yes, I am using OS X. When using HC on the same computer (in Classic) 
> every
> day has 86400 seconds. Is this just an OS X issue.
> I am using Revolution 2.2.
> I am sorry I didn't notice this discussion previously (I've been on 
> the list
> for over a year but don't read everything that is posted), didn't mean 
> to
> restart old threads.
> Was there a workaround? Some type of immutable seconds, where each day 
> and
> every day contains exactly 86400 seconds? RevSeconds? GMTSeconds?
> Paul Looney
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> http://lists.runrev.com/mailman/listinfo/use-revolution
>
>
>