[Python-Dev] PyObject_New vs PyObject_NEW
Guido van Rossum
guido@python.org
Wed, 12 Mar 2003 08:08:20 -0500
Wed, 12 Mar 2003 08:08:20 -0500
- Previous message: [Python-Dev] PyObject_New vs PyObject_NEW
- Next message: [Python-Dev] PyObject_New vs PyObject_NEW
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
> Someone I work with recently caused a test to start asserting in VC7's > instrumented free() call, using a pydebug build. He explained the > change this way: > > "I switched from PyObject_New to PyObject_NEW, which according to it's > documentation omits the check for type_object != 0 and consequently > should run a little bit faster" > > [he doesn't ever pass 0 as the typeobject] > > Did he miss some other important fact about PyObject_NEW? Does the > doc need to be fixed? You can read the source code as well as I can. --Guido van Rossum (home page: http://www.python.org/~guido/)
- Previous message: [Python-Dev] PyObject_New vs PyObject_NEW
- Next message: [Python-Dev] PyObject_New vs PyObject_NEW
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]