This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author dalcinl
Recipients dalcinl, larry
Date 2009-03-31.21:48:59
SpamBayes Score 0.0059180004
Marked as misclassified No
Message-id <1238536142.48.0.0182309702045.issue5630@psf.upfronthosting.co.za>
In-reply-to
Content
Two questions:

1) Why do you prefer to pass destructor as a first argument?

2) Do we really need two different calls for providing a context
pointer? Why no just one call and pass a NULL context?

A comment:

Suppose one wants to implement export/import module C-API's in a
function-by-function basis. This is nice, as you can extend your module
C-API, and make it be backward "ABI" compatible.

As the void* <-> void(*)(void) conversion is illegal(?) in C(99?), one
has to go to the oddities of doing some sort of type-punning with
unions... this could be somewhat tedious for hand-written extension
modules. 

Do you have any idea on how extend the CObject API for the commented use
case?
History
Date User Action Args
2009-03-31 21:49:02dalcinlsetrecipients: + dalcinl, larry
2009-03-31 21:49:02dalcinlsetmessageid: <1238536142.48.0.0182309702045.issue5630@psf.upfronthosting.co.za>
2009-03-31 21:49:00dalcinllinkissue5630 messages
2009-03-31 21:48:59dalcinlcreate