Comments by Miszou (Top 1 by date)

Well, the function actually already accepts a string as a workaround to this problem, but I was trying to tidy it up and make it more intuitive to the caller.

You're right that I can use a string, call In32.TryParse on the value and then deal with it as necessary. But it would seem to be "better" to use an Int in the first place and let the framework handle the erroneous input. I just want it to handle it in a slightly friendlier fashion!