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

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

[Python-checkins] python/dist/src/Objects bufferobject.c,2.19,2.20 complexobject.c,2.62,2.63 floatobject.c,2.114,2.115 intobject.c,2.91,2.92 stringobject.c,2.180,2.181 tupleobject.c,2.71,2.72

• Previous message: [Python-Dev] PEP 218 (sets); moving set.py to Lib
• Next message: [Python-Dev] Re: [Python-checkins] python/dist/src/Objects bufferobject.c,2.19,2.20 complexobject.c,2.62,2.63 floatobject.c,2.114,2.115 intobject.c,2.91,2.92 stringobject.c,2.180,2.181 tupleobject.c,2.71,2.72
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    guido> Call me anal, but there was a particular phrase that was speading
    guido> to comments everywhere that bugged me: /* Foo is inlined */
    guido> instead of /* Inline Foo */.  Somehow the "is inlined" phrase
    guido> always confused me for half a second (thinking, "No it isn't"
    guido> until I added the missing "here").  The new phrase is hopefully
    guido> unambiguous.

Perhaps a comment at the definition of Foo that says "this code has been
inlined elsewhere" makes sense so that if people fix bugs or enhance them
they will be prompted to scout around for other places that need fixing.  (I
hesitate to suggest that all the places a piece of code is inlined should be
recorded, but perhaps that's another option.)

Skip

• Previous message: [Python-Dev] PEP 218 (sets); moving set.py to Lib
• Next message: [Python-Dev] Re: [Python-checkins] python/dist/src/Objects bufferobject.c,2.19,2.20 complexobject.c,2.62,2.63 floatobject.c,2.114,2.115 intobject.c,2.91,2.92 stringobject.c,2.180,2.181 tupleobject.c,2.71,2.72
• 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