Re: Parsing Date Strings with Time Zones in c++
On Oct 10, 7:18 pm, =D6=F6 Tiib <oot...@hot.ee> wrote:
On 10 okt, 17:36, James Kanze <james.ka...@gmail.com> wrote:
On Oct 10, 2:44 am, =D6=F6 Tiib <oot...@hot.ee> wrote:
On 10 okt, 03:11, Jorgen Grahn <grahn+n...@snipabacken.se> wrote:
Well, it goes without saying that there's always *some*
point where it breaks down, doesn't it? If they announce
tomorrow that .se will have DST all year around,
/someone/ will have to change something in software.
(What are the alternatives, anyway?)
Just instead of recording some "Stockholm time" record raw
Zulu time or local with offset mentioned "+01" "+0100"
The problem isn't what you send, it's what you receive. Have
you actually seen any systems behaving this way?
I have no copy under hand so i just humbly believe that it is like ISO
Sorry, I misread what you'd written. I read it as recording raw
Zulu time with an offset so that you could know what the local
time was. What you've actually described is ISO 8601, and it is
occasionally used (albeit not as wide spread as one would like).
It's feasible for the system to keep track of past
rules. I don't know if they typically do, and
frankly I don't care enough to check.
They typically don't.
Then Unix isn't typical. Do you have some concrete information
concerning Windows, or are you just speculating?
If there is Olson database present in Windows? No.
You worry me. The correct functionning of the system I'm
working on depends on being able to calculate the correct date
and time for any given time zone. (Or maybe it's not a problem,
since we're normally only concerned with times in the "standard
business" hours. A one hour error due to summer time won't
change the day, and so shouldn't cause us problems.)
Also HP-UX was bundled without.
The HP-UX I've worked on had it, but I don't know if it was
I doubt that all the mobile devices currently up- rocketing
Maybe not resident, but they know how to get it when they need
They only real problem would be for devices not connected to the
Last i dealt with timezones in Windows then Windows
had some self-breed timezone ID that was outright ambiguous. Since
zoneinfo is public domain database one may of course kick it up and
bundle with his software (and update with service packs). It is not
convenient for each application but fine for bigger special purpose
package. Raw offset is winner anyway, nothing to do.
ISO date format, in general, yes. You're certainly right about
that (and I'm sorry I misread your suggestion), But not all
sources are kind enough to supply it.