Forums Bug Reports DATE bug

...etc
1698-1902 - don't write time and date
1903-1969 - bad time and date
1970-2037 - OK
2038-2650 - don't write time and date
2651-2854 - bad time and date
...etc
Functions:
$asctime
$ctime
$date
$day
$fulldate
$gmt
$time
$timestamp
$timezone

What?

change date on your PC to 2038...

According to the help file, from /help $ctime


Since $ctime won't return a negative value (something that I know I've seen mentioned on these boards) then it makes sense that a date with year before January 1 1970 is not going to return a correct response. The fact that you went so far back in time that you found dates that return nothing rather than an error is interesting, but, in my opinion, not very relevant.

As to the dates in the future, ie: 2038, I would imagine that the coding for mIRC will be updated to accomodate those dates as we get closer to them. Right now, by the calendar that I use, that's still over 3 decades away.

The problem is that a number that represents the year 2038 is too big to fit in a 32bit integer. As RusselB said the code will most likely be updated when it needs to be, which is not for 32 years yet

On my PC there is a date - on March, 7th 7506 years. How to make so that mIRC wrote time (timestamp) in messages? It would be very much desirable to know the answer...

If you can tell me how you managed to get a date in the 76th century to go on your computer, then I might be able to help. I tried changing the date on my computer to match what you said you have, and it wouldn't go. Nothing above 2099 was accepted as a valid date on my system.

This is getting out of my area of knowledge, but someone else might know how to do this. I suspect that you'll have to use com objects to get the current date from the system (since $date, $ctime, etc. return either $null, errors or incorrect numbers ($ctime returned a negative number when tested after changing the date on my system with the program you provided the link for via pm)), then put the date into a variable, which could be used as a timestamp.

Again, let me say, that I'm not familiar with com objects or how they work, but that was the only thing I was able to find that looked like it might work.

somebody make please dll which returns time in a format [HH:nn:ss]

/alias [HH:nn:ss] { return $time([HH:nn:ss]) }

usage //echo the time is $[HH:nn:ss]

* Amazing eh! *