Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://mail.python.org/pipermail/python-dev/2005-September/056548.html below:

[Python-Dev] "and" and "or" operators in Py3.0

• Previous message: [Python-Dev] "and" and "or" operators in Py3.0
• Next message: [Python-Dev] "and" and "or" operators in Py3.0
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

> That leaves error reduction and clarity as the main motivations for
> changing 'and' and 'or' to act like '&&' and '||' and for introducing a
> conditional operator to handle everyone's favorite use cases.

I predict that people who use "and" and "or" correctly today will
start confusing "&&" with "&" and "||" with "|", which in many
instances will pass silently.  In fact, I'll wager that lots of people
who are familiar with boolean and/or will have never used bitwise
and/or.

Skip

• Previous message: [Python-Dev] "and" and "or" operators in Py3.0
• Next message: [Python-Dev] "and" and "or" operators in Py3.0
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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