Yeah, I suppose you could call that a bug. What it should do is to return an error or else return it in scientific notation.
Reminds me of this bug:
//echo -e t: $asctime(2999999999)
Khaled didn't account for the outer limits of the variables in a way that's consistant with most languages. After "Mon Jan 18 22:14:06 2038" mIRC will no longer be able to tell what time it is since 2147483647 is the upper limit of the variable that's used. This is also the issue with an uptime over 49 days. Same size variable is used with both, only one's signed and the other is unsigned. Then again, what are the chances that Khaled will still be coding mIRC in 30 some years? ;-) For that matter, it's not often you see a Winblows system with over 49 days of uptime tho I have had mine go over 9 weeks ;-) That's one that'd I would love to see fixed tho as when it does happen all timers also stop and it's a PITA to have to restart them all.
Cheers,
GregMo
