A RetroSearch Logo

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

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2001-February/012706.html below:

[Python-Dev] Coercion and comparisons

[Python-Dev] Coercion and comparisonsKa-Ping Yee ping@lfw.org
Tue, 6 Feb 2001 11:24:25 -0800 (PST)
On Tue, 6 Feb 2001, Ka-Ping Yee wrote:
>     Category        Python operators        E operators
> 
>     identity        is, is not              ==, !=
>     value           ==, !=, <>              x.equals(y), !x.equals(y)
>     magnitude       <, <=, >, >=            <, <=, >, >=, <>, <=>
> 
> Each type of equality has a specific and useful meaning.  Most
> languages, including Python, acknowledge the first two.  But you
> can see how the coercion problem raised above is a consequence
> of the fact that the third category is incomplete.

I didn't state that last sentence very well, and the table's a bit
inaccurate.

Rather, it would be better to say that '==' and '!=' end up having
to do double duty (sometimes for value equality, sometimes for
magnitude equality) -- when really '==' doesn't belong with
ordering operators like '<'.  It's quite a separate concept.


-- ?!ng

"There's no point in being grown up if you can't be childish sometimes."
    -- Dr. Who




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