[Python-Dev] Baffled by PyArg_ParseTupleAndKeywords modification
"Martin v. Löwis"
martin at v.loewis.de
Sat Feb 11 23:52:45 CET 2006
More information about the Python-Dev mailing list
Sat Feb 11 23:52:45 CET 2006
- Previous message: [Python-Dev] Baffled by PyArg_ParseTupleAndKeywords modification
- Next message: [Python-Dev] Baffled by PyArg_ParseTupleAndKeywords modification
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Aahz wrote: >>That future version might get published in 2270, when everybody has >>switched to C++, and compatibility with C is no longer required. > > > Just for the clarification of those of us who are not C/C++ programmers, > are you saying that this is different from the meaning in Python, where > "deprecated" means that something *IS* going away? To repeat the literal words from the standard: Annex D [depr]: 1 This clause describes features of the C++ Standard that are specified for compatibility with existing implementations. 2 These are deprecated features, where deprecated is defined as: Normative for the current edition of the Standard, but not guaranteed to be part of the Standard in future revisions. Regards, Martin
- Previous message: [Python-Dev] Baffled by PyArg_ParseTupleAndKeywords modification
- Next message: [Python-Dev] Baffled by PyArg_ParseTupleAndKeywords modification
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list