Guido van Rossum guido at python.org
Mon Apr 4 11:47:01 EDT 2016

• Previous message (by thread): [Python-Dev] Py_SETREF vs. Py_XSETREF
• Next message (by thread): [Python-Dev] review/proof docs about private memory heap
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

Agreed, let's go with two macros. The time discussing this further
could be spent more productively.

On Mon, Apr 4, 2016 at 2:35 AM, Victor Stinner <victor.stinner at gmail.com> wrote:
> If some dev don't want to use the single macro for good or bad reasons, it's
> maybe better to have two macros to generalize their usage. The macro makes
> to C code shorter and easier to review.
>
> Victor
>
>
> _______________________________________________
> Python-Dev mailing list
> Python-Dev at python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> https://mail.python.org/mailman/options/python-dev/guido%40python.org
>



-- 
--Guido van Rossum (python.org/~guido)

---

• Previous message (by thread): [Python-Dev] Py_SETREF vs. Py_XSETREF
• Next message (by thread): [Python-Dev] review/proof docs about private memory heap
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list