Oops, obviously I haven't read my own copy of "The C Programming Language" often enough, nor my own copy of Deitel's C++ Programming guide, nor my copies of the MC68000 design books. That is not to mention the other books in my library that deal with computer design.

What argv0 was originally telling you, and that you refuse to listen to, is that the behaviour of the function is undefined for inputs greater than 32-bit.

Genius_at_work notes that mIRC handles this undefined behaviour in a consistent manner.

Your point that it would be useful to have the behaviour of the function defined differently for invalid input is understood by all here. However, because this is a design feature - it is a Suggestion, rather than a bug. Sometimes a fine line?

Perhaps you should learn how computers work and note the inputs of others before you accuse anyone of saying "stupid things".

Cheers,

DK


Darwin_Koala

Junior Brat, In-no-cent(r)(tm) and original source of DK-itis!