2038

[Geert Janssens]

On 06-11-12 16:09, John Ralls wrote:
> On Nov 6, 2012, at 1:30 AM, Geert Janssens <janssens-geert at telenet.be> wrote:
>
>
>> I wasn't aware of your work on the 2038 date issue. I have just discovered your fix-dates branch on github. That's a very big work. And I didn't know OS X and Windows aren't looking ahead that far. I'm slightly surprised glib has has no provisions for this. After all that is an important portability library for writing portable applications in C. But I'm sure you have looked around before starting your own implementation.
> Oh, OSX and Win32 have their own 64-bit date-time APIs, they just haven't pushed them on to time_t.
>
> I *am* using GLib: That's where GDateTime comes from. However, GTimezone only worked with Linux (because it uses the TZif2 with 64-bit DST intervals) until I fixed it in GLib 2.34.1 to work with TZif  and therefore BSD and OSX [1].
>
> The implementation for Win32 [2][3][4] is a lot more involved, so it's going to go into GLib 2.36. Fortunately Gnucash needs only a small part of it, and I'd written the work-around for that part before Arnel got started.
>
> Regards,
> John Ralls
>
> [1] https://bugzilla.gnome.org/show_bug.cgi?id=631382
> [2] https://bugzilla.gnome.org/show_bug.cgi?id=683998
> [3] https://bugzilla.gnome.org/show_bug.cgi?id=686128
> [4] https://bugzilla.gnome.org/show_bug.cgi?id=686184
>   
>
Right. I'm a bit slow it seems. I finally can frame your recent request 
on the timezone info on Windows. It's for the glib GTimezone work.

I haven't looked into the details, as it would take me much more time to 
grasp what has changed than you would need to answer this question: so 
eventually GLib will have the proper portable date/time/timezone 
functions we need. Will it be easy at that time to swap our workaround 
code for the GLib stuff ? Considering your deep involvement in the glib 
work, I'd expect so.

Geert