[prev in list] [next in list] [prev in thread] [next in thread] 

List:       python-bugs-list
Subject:    [issue17589] Make documentation about macros in C API explicit about rvalue vs statement
From:       Antoine Pitrou <report () bugs ! python ! org>
Date:       2013-03-31 20:40:45
Message-ID: 1364762445.03.0.804408849458.issue17589 () psf ! upfronthosting ! co ! za
[Download RAW message or body]


Antoine Pitrou added the comment:

Py_INCREF usable as an rvalue sounds more like an accident than a deliberate feature, \
and it would be IMO counter-productive to codify this behaviour in the docs.

As for the lvalue usage of Py_REFCNT and Py_SIZE, I think it would be better if it \
were limited to CPython core. But arguably writers of extension types may want to \
mutate the size field of a varsize object.

----------
nosy: +pitrou

_______________________________________
Python tracker <report@bugs.python.org>
<http://bugs.python.org/issue17589>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/python-bugs-list%40marc.info



[prev in list] [next in list] [prev in thread] [next in thread]