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-January/011890.html below:

[Python-Dev] Rich comparison confusion

[Python-Dev] Rich comparison confusion [Python-Dev] Rich comparison confusionGuido van Rossum guido@digicool.com
Fri, 19 Jan 2001 13:48:45 -0500
>  > ... I can see no valid reason why someone would want to overload
>  > a>b different than b<a, ... 
>  > 
> 
> I agree.  But this assumes that the result of A<B and B>A is a
> collection of Booleans.  In the Interactive Data Language (IDL) these
> operators are essentially mapped to ceiling and floor functions which
> are not commutative.  I personally find this silly, but IDL users
> coming to Python may be surprised when the comparison of two Numeric
> arrays returns a Boolean-like result.

This means that Python can't be used to emulate this part of IDL.  I
don't understand how these can be not commutative unless they have a
side effect on the left argument, and that's not possible in Python
anyway.

--Guido van Rossum (home page: http://www.python.org/~guido/)



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