epoch Prime

[Dieter]

(01-06-2018 02:45 PM)salvomic Wrote:  nobody fo you said me that I made an "old error of mine": to use 84600 instead of 86400!
I made this error in some astronomical programs and then I was aware of the bug after ...days... :-(

What? Nobody told you? Sure I did! Didn't you read my post?

(01-06-2018 09:41 AM)Dieter Wrote:  

(01-06-2018 09:28 AM)salvomic Wrote:  

Code:

ti:=(epoch MOD 84600)/3600;

...
epoch2date(1515230706) returns {2018.0106, 12.41833333}
→HMS(12.41833333) returns 12°25'06'', that two hours later, but still I must set UTC problem...

It's not a timezone problem. Take a closer look at the quoted code line. ;-)

"Take a closer look at the quoted code line" – wasn't this clear enough?

(01-06-2018 02:45 PM)salvomic Wrote:  Again, it would be better to have optional input, instead of remembering to put some "magic numbers" as -1 ...

I think it's better that the timezone is not optional but required. And this "magic" number is not that magic – it's simply your local timezone. We can safely assume that virtually everyone who uses such a program for converting date and time is aware of his local timezone.

Dieter