Alan Hourihane, 17.04.2013 17:36:10:
mktime() is a very bad performer - known fact. One of the packages I was building decided mktime() was too slow and deemed it unusable because it took longer than 60 seconds (when compiled with m68000, m68020-60 is quicker, but still slow.)
I remember that the mintlib-time-functions try to get an environment-variable (TZ?) on every call. When this is not present, it's unusably slow in time-critic situations, if it is maybe too.
But that was long ago, maybe things have changed. -- Helmut Karlowski