"I'm right. It's undefined, and that's the way it is" - this is the message I get from you. Well, it might not be that way in the future, if a compiler that Khaled chooses to use defines the behaviour of atoi() differently. Why not make an effort to use a function that defines the behaviour, or better yet takes advantage of C/C++'s silent wrapping to produce a correct behaviour, providing one of the two arguments isn't truncated? Well, if you want to be an idiot... then feel free to argue against a change that would eliminate undefined changes for $and/$or/$xor...

Last edited by s00p; 26/09/09 04:53 AM.