[Python-Dev] PyObject_New vs PyObject_NEW
David Abrahams
dave@boost-consulting.com
Wed, 12 Mar 2003 07:24:48 -0500
Wed, 12 Mar 2003 07:24:48 -0500
- Previous message: [Python-Dev] bsddb3 test errors - are these expected?
- 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? -- Dave Abrahams Boost Consulting www.boost-consulting.com
- Previous message: [Python-Dev] bsddb3 test errors - are these expected?
- Next message: [Python-Dev] PyObject_New vs PyObject_NEW
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]