Home/ Questions/Q 489805
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T01:50:44+00:00

Why was it decided that when parsing a boolean, 0/1 are not acceptable? When

  • 0

Why was it decided that when parsing a boolean, 0/1 are not acceptable?

When parsing any integer type value, it accepts numerical strings to be parsed. (And if .NET can parse the string “One hundred million two hundred and sixty five thousand eight hundred and sixty five” I would be surprised).

What makes booleans special? They are essentially 0 as false, and non-zero as true in my experience…

Is there a bcl method to parse a string like this, and if not, why?

Note: I forgot to specify in a string “0” and “1”. Curious though that if already an int it works as I anticipated. Maybe this caused the confusion.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    0 and (not-zero) are not equal to “false” and “true”, they’re just the representation chosen by C. Other languages use 0 for true and -1 for false, or other schemes entirely. A boolean is not a 0 or a 1, it’s a true or a false.

    Should it also handle “yes” and “no”, “off” and “on”, and all of the myriad other things that are analogous to booleans? Where would you draw the line?

    • 0