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/2003-December/040649.html below:

[Python-Dev] Int FutureWarnings and other 2.4 TODOs

[Python-Dev] Int FutureWarnings and other 2.4 TODOs [Python-Dev] Int FutureWarnings and other 2.4 TODOsAndrew Koenig ark-mlist at att.net
Wed Dec 3 10:41:43 EST 2003
> > Isn't the 'long' format the more general representation, with the 'int'
> > format then being a performance hack to take advantage of the speed of C
> > integer arithmetic?
> >
> > I'm just wondering if a different way of thinking about it might help
> > with figuring out how to handle a combined implementation.
> 
> I proposed that too, but Andrew Koenig didn't like it.

It's not me, it's Barbara Liskov at MIT.

The general notion is that if Y is derived from X, then you should be able
to use a Y wherever you might otherwise want to use an X.  In other words, Y
should support every operation that X supports, but Y can add operations of
its own.


More information about the Python-Dev mailing list

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