[Python-Dev] re: PEP 279 revisited, formally (original) (raw)
Steve Holden sholden@holdenweb.com
Fri, 26 Apr 2002 14:14:35 -0400
- Previous message: [Python-Dev] re: PEP 279 revisited, formally
- Next message: [Python-Dev] re: PEP 279 revisited, formally
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
----- Original Message ----- From: "Tim Peters" <tim.one@comcast.net> To: <python-dev@python.org> Sent: Friday, April 26, 2002 11:58 AM Subject: RE: [Python-Dev] re: PEP 279 revisited, formally
[Guido] > ... > So enumerate() it is. (Specifically not enum() because of the C/C++ > meaning of that word.)
The C/C++ meaning isn't a barrier to me: a C enum decl without embedded '=' must associate 0 with the first name, 1 with the second name, and so on. Indeed, if the Python enum returned pairs in (value, index) order, dict(enum(['apple', 'pear', 'godzilla']) would create the dict {'apple': 0, 'pear': 1, 'godzilla': 2} which is about as close to the C enum {apple, pear, godzilla}; /* now apple==0, pear==1, godzilla==2 */ as you can get with a Python function.
+1
home: http://www.holdenweb.com/ Python Web Programming: http://pydish.holdenweb.com/pwp/
- Previous message: [Python-Dev] re: PEP 279 revisited, formally
- Next message: [Python-Dev] re: PEP 279 revisited, formally
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]