Message99312
| Author |
mark.dickinson |
| Recipients |
MrJean1, ajaksu2, barry, benjamin.peterson, mark.dickinson, meador.inge, pitrou, teoliphant |
| Date |
2010年02月13日.11:07:30 |
| SpamBayes Score |
8.459003e-08 |
| Marked as misclassified |
No |
| Message-id |
<1266059274.29.0.344917421658.issue3132@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Some of the proposed struct module additions look far from straightforward; I find that section of the PEP significantly lacking in details and motivation.
"Unpacking a long-double will return a decimal object or a ctypes long-double."
Returning a Decimal object here doesn't make a lot of sense, since Decimal objects aren't generally compatible with floats. And ctypes long double objects don't seem to exist, as far as I can tell. It might be better not to add this code.
Another bit that's not clear to me: how is unpacking an object pointer expected to work, and how would it typically be used? What if the unpacked pointer no longer points to a valid Python object? How would this work in other Python implementations?
For the 'X{}' format (pointer to a function), is this supposed to mean a Python function or a C function?
What's a 'specific pointer'? |
|