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 | brett.cannon |
|---|---|
| Recipients | brett.cannon, jlaurila |
| Date | 2008年07月09日.19:55:54 |
| SpamBayes Score | 0.009163603 |
| Marked as misclassified | No |
| Message-id | <1215633419.23.0.363387176083.issue3329@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Is registering pointers to functions really necessary, or would defining macros work as well? From a performance perspective I would like to avoid having a pointer indirection step every time malloc/realloc/free is called. I guess my question becomes, Jukka, is this more for alternative implementations of Python where changes to source are already expected, or for apps that embed Python where a change of malloc/realloc/free varies from app to app that dynamically loads Python? |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年07月09日 19:56:59 | brett.cannon | set | spambayes_score: 0.0091636 -> 0.009163603 recipients: + brett.cannon, jlaurila |
| 2008年07月09日 19:56:59 | brett.cannon | set | spambayes_score: 0.0091636 -> 0.0091636 messageid: <1215633419.23.0.363387176083.issue3329@psf.upfronthosting.co.za> |
| 2008年07月09日 19:55:55 | brett.cannon | link | issue3329 messages |
| 2008年07月09日 19:55:55 | brett.cannon | create | |