__TIMESTAMP_UNIXEPOCH__ instead of useless __TIMESTAMP__?
Steven Schveighoffer
schveiguy at yahoo.com
Sat Jan 27 12:45:14 UTC 2018
On 1/27/18 4:05 AM, Kagamin wrote:
> Just a numeric (long) result from `time` - more compact storage and
> simpler implementation.
A numeric value is fine, but I would be cautious about relying on
time(). It's not guaranteed to return 64 bits, meaning the y2k35 bug
would affect D ;)
However, having a nice actual timestamp string may be more useful. My
suggestion also contains the timezone, so it has more info (and this was
a further request by the OP).
-Steve
More information about the Digitalmars-d
mailing list