I wondered to myself today while reading through the Python
tutorial whether it would be a good idea to have a separate
boolean type in Py3K. Would this help catch common mistakes?
I won't presume to truly understand the new-to-Python experience,
but one might *guess* that
>>> 5 > 3
true
would make a little more sense to a beginner than
>>> 5 > 3
1
Of course this means introducing "true" and "false" as keywords
(or built-in values like None -- perhaps they should be spelled
True and False?) and completely changing the way a lot of code
runs by introducing a bunch of type checking, so it may be too
radical a change, but --
And i don't know if it's already been discussed a lot, but --
I thought it wouldn't hurt just to raise the question.
-- ?!ng
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4