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 | gregcouch |
|---|---|
| Recipients | gregcouch, mthibaut, theller |
| Date | 2007年11月29日.19:31:47 |
| SpamBayes Score | 0.098189235 |
| Marked as misclassified | No |
| Message-id | <1196364707.93.0.873257729806.issue1506@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
That's a disappointment. <ffi_common.h> has the right logic in it already. Perhaps it should be copied to callproc.c. I'm less concerned about alloca not being there at all because it seems to be a pervasive extension in non-gcc compilers, but using malloc is fine too. Please go ahead and fix this as you see fit. I've started issue 1516 about using non-gcc compilers to compile _ctypes/libffi. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2007年11月29日 19:31:48 | gregcouch | set | spambayes_score: 0.0981892 -> 0.098189235 recipients: + gregcouch, theller, mthibaut |
| 2007年11月29日 19:31:47 | gregcouch | set | spambayes_score: 0.0981892 -> 0.0981892 messageid: <1196364707.93.0.873257729806.issue1506@psf.upfronthosting.co.za> |
| 2007年11月29日 19:31:47 | gregcouch | link | issue1506 messages |
| 2007年11月29日 19:31:47 | gregcouch | create | |