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

Showing content from http://mail.python.org/pipermail/python-dev/2002-August/027797.html below:

[Python-Dev] hex constants, bit patterns, PEP 237 warnings and gettext

• Previous message: [Python-Dev] hex constants, bit patterns, PEP 237 warnings and gettext
• Next message: [Python-Dev] hex constants, bit patterns, PEP 237 warnings and gettext
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

>>>>> "TP" == Tim Peters <tim.one@comcast.net> writes:

    TP> [Barry A. Warsaw]
    >> ...  So if "0x950412de" isn't the right way to write a 32 bit
    >> pattern,

    TP> It isn't today, but will be in 2.4.

But isn't that wasteful?  Today I have to add the L to my hex
constants, but in a year from now, I can just turn around and remove
them again.  What's the point?

The deeper question is: what's wrong with "0x950412de"?  What bits
have I lost by writing my hex constant this way?  I'm trying to
understand why hex constants > sys.maxint have to deprecated.

-Barry

• Previous message: [Python-Dev] hex constants, bit patterns, PEP 237 warnings and gettext
• Next message: [Python-Dev] hex constants, bit patterns, PEP 237 warnings and gettext
• 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