[Python-3000] PEP 3123: Making PyObject_HEAD conform to standard C (Was: Dropping PyObject_HEAD) (original) (raw)
Giovanni Bajo rasky at develer.com
Sun Apr 29 21:16:52 CEST 2007
- Previous message: [Python-3000] PEP 3123: Making PyObject_HEAD conform to standard C (Was: Dropping PyObject_HEAD)
- Next message: [Python-3000] PEP 3123: Making PyObject_HEAD conform to standard C (Was: Dropping PyObject_HEAD)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 29/04/2007 19.57, Martin v. Löwis wrote:
That is an open issue. PyObjectHEAD clearly is more backwards-compatible. However (besides its current non-C-conformance), I never liked it, because of the missing semicolon (I thought it confuses Emacs, but can't reproduce the problem anymore, though - perhaps it did confuse Emacs in the past?)
So I personally would phase it out for style reasons, but others may think differently; if I hear opinions in either direction, I'm happy to code them into the PEP.
The fact that it existed made it possible to do this transition though. Haven't we had this macro in the first place, now you would need to break all third party modules without an easy fallback.
So, I'm probably +0 on keeping it since history tends to repeat itself :)
Giovanni Bajo
- Previous message: [Python-3000] PEP 3123: Making PyObject_HEAD conform to standard C (Was: Dropping PyObject_HEAD)
- Next message: [Python-3000] PEP 3123: Making PyObject_HEAD conform to standard C (Was: Dropping PyObject_HEAD)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]