[Python-Dev] PEP 384: Defining a Stable ABI

[Nick Coghlan]

[PEP]
>>>>> Function-like macros (in particular, field access macros) remain
>>>>> available to applications, but get replaced by function calls
>>>>> (unless their definition only refers to features of the ABI, such
>>>>> as the various _Check macros)
[MAL]
>>>> Including Py_INCREF()/Py_DECREF() ?
[Nick]
>>> I believe so - MvL deliberately left the fields that the ref counting
>>> relies on as part of the ABI.
[MAL]
>> Hmm, another slow-down.
[MvL]
> ??? Why is "no change" a slow-down?

That was just a miscommunication - I misunderstood the sense in which
MAL was using "Including". He was referring to the first part of the
paragraph from the PEP (most macros become functions), but I answered
assuming he was referring to the part in parentheses (some macros get to
stay).

So to be perfectly clear: the Py_INCREF/Py_DECREF macros are available
as part of the stable ABI because they qualify for the PEP's "definition
only refers to features of the ABI" exception.

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia
---------------------------------------------------------------