[Python-Dev] Baffled by PyArg_ParseTupleAndKeywords modification (original) (raw)
Greg Ewing greg.ewing at canterbury.ac.nz
Sat Feb 11 00:46:20 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 ]
Martin v. Löwis wrote:
FWIW, Annex D also defines these features as deprecated: - the use of "static" for objects in namespace scope (AFAICT including C file-level static variables and functions) - C library headers (i.e. <stdio.h>)
Things like this are really starting to get on my groat. It used to be that C++ was very nearly a superset of C, so it was easy to write code that would compile as either. But C++ seems to be evolving into a different language altogether.
(And an obnoxiously authoritarian one at that. If I want to write some C++ code that uses stdio because I happen to like it better, why the heck shouldn't I be allowed to? It's MY program, not the C++ standards board's!)
Sorry, I just had to say that.
Greg
- 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 ]