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)
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