Forums Feature Suggestions change === behavior with numbers

So, I was messing around with some script, and I discovered that...

if (123456789123456789123456789123 == 123456789123456789123456789122) echo -a true

echoes true, even though they are not the same number (check the last digit). Now, I can understand that, since mirc has to treat them as numbers for comparisons like (0.1 == .1) to work, and as most any language does, mirc has limits to the size of number it can handle, so that's fine. My suggestion is that === should, in addition to being case-sensitive for text, treat numbers as text as well, so that

if (123456789123456789123456789123 === 123456789123456789123456789122) echo -a true

does nothing, since the two strings are not exactly the same.

Questions? Comments? Abuse?

edit: also, in case it was not clear, (0.1 === .1) would be false with this change.