mIRC Home    About    Download    Register    News    Help

Print Thread
#116045 01/04/05 01:52 PM
Joined: Jun 2004
Posts: 8
Nescafe Offline OP
Nutrimatic drinks dispenser
OP Offline
Nutrimatic drinks dispenser
Joined: Jun 2004
Posts: 8
Waiting for my Empty "ACTION" PRIVMSG not displayed topic to get it's first answer, I just remembered an uncomplete feature that I really would appreciate being fixed :

$ctime, $date and other $asctime just can't handle negative time values.

I have of course written my own time routines, but as time goes, that sounds more and more overkill to me. Most systems fluently use negative time values as seconds before January 1 1970, mIRC should be one of those.

#116046 01/04/05 02:13 PM
Joined: Apr 2004
Posts: 871
Sat Offline
Hoopy frood
Offline
Hoopy frood
Joined: Apr 2004
Posts: 871
Quote:
Most systems fluently use negative time values as seconds before January 1 1970

And most of those same systems will stop working properly in 2038 (link).


Saturn, QuakeNet staff
#116047 01/04/05 06:00 PM
Joined: Dec 2002
Posts: 2,962
S
Hoopy frood
Offline
Hoopy frood
S
Joined: Dec 2002
Posts: 2,962
The size of the integer used to represent UNIX time is unrelated as to whether negative values should behave as dates before the UNIX epoch. If mIRC accepts negative values in this way using a 32bit integer, it will still behave the same way with those values if/when it switches to a 64-bit integer in the future.


Spelling mistakes, grammatical errors, and stupid comments are intentional.
#116048 01/04/05 10:52 PM
Joined: Apr 2004
Posts: 871
Sat Offline
Hoopy frood
Offline
Hoopy frood
Joined: Apr 2004
Posts: 871
It is actually very related, but I didn't know that mIRC actually has the same problem (time values of 2^31 and up don't work either). I was merely pointing out that "other programs do it too" is not necessarily a good argument; I agree that the feature suggestion itself makes sense..


Saturn, QuakeNet staff

Link Copied to Clipboard