Subj : JS Object save_msg()
To : Digital Man
From : deon
Date : Mon Dec 23 2024 07:11 am
Re: JS Object save_msg()
By: Digital Man to deon on Sat Dec 21 2024 02:51 pm
Howdy,
> No, it would not. The mktime() standard C library function uses *your* local
> time zone (not mine) in the conversion to time_t. There isn't a standard C
> runtime library function that takes a broken-down date/time and converts it
> to a time_t using an arbitrary (user supplied) time zone. The rest of your
> message seemed dependant on this first incorrect assumption.
Oh, that was a bad assumption on my part. I did think when_import_time was a valid time_t value. (IE: The utc time the message was written.)
I wanted to check it out, so I set up my test system to UTC-8:00, and exported a messages to FTN to clrghouz, then into Alterant (UTC+11:00), and indeed, on my test system:
when_written 6764CEAC FE20 Thu Dec 19 17:55:56 2024 UTC-8:00
Is a valid time_t for the printed time, and on alterant
when_written 6763C37C FE20 Thu Dec 19 17:55:56 2024 UTC-8:00
it is not.
Incidently, the time_t on alterant 1734591356, is exactly 19hrs incorrect, which just so happens to be the difference in our timezones.
...����
---
� Synchronet � AnsiTEX bringing back videotex but with ANSI
