A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2009-May/089716.html below:

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

[Python-Dev] [unladen-swallow] PEP 384: Defining a Stable ABI [Python-Dev] [unladen-swallow] PEP 384: Defining a Stable ABIskip at pobox.com skip at pobox.com
Wed May 20 22:59:32 CEST 2009
    Nick> Jeffrey Yasskin wrote:

    >> To decrease the annoyance of having to change source code, we could
    >> have Py_INCREF(x) expand to Py_IncRef(x) in ABI-compatibility mode.

    Nick> Forcing developers to choose between the speed of the
    Nick> INCREF/DECREF macros and the proposed ABI compatibility mode for
    Nick> the benefit of an as yet hypothetical GIL-less CPython API
    Nick> implementation seems more like a way to kill adoption of the ABI
    Nick> compatibility mode rather than a way to encourage the use of the
    Nick> IncRef/Decref functions.

I suspect it's not really germane to this discussion but if the
incref/decref functions were defined as inline would that effectively be
like using the macro versions vis a vis ABI compatibility?

Skip
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4