[Python-Dev] PEP 579 and PEP 580: refactoring C functions and methods
INADA Naoki
songofacandy at gmail.com
Thu Sep 13 19:50:50 EDT 2018
More information about the Python-Dev mailing list
Thu Sep 13 19:50:50 EDT 2018
- Previous message (by thread): [Python-Dev] PEP 579 and PEP 580: refactoring C functions and methods
- Next message (by thread): [Python-Dev] Request for review
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
2018年9月13日(木) 18:22 Jeroen Demeyer <J.Demeyer at ugent.be>: > On 2018-09-13 02:26, Petr Viktorin wrote: > > > PyCCall_FASTCALL is not a macro, shouldn't it be named PyCCall_FastCall? > > What's the convention for that anyway? I assumed that capital letters > meant a "really know what you are doing" function which could segfault > if used badly. > > For me, whether something is a function or macro is just an > implementation detail (which can change between Python versions) which > should not affect the naming. > https://www.python.org/dev/peps/pep-0007/#naming-conventions All capital name is used for macros. > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20180914/abb32adc/attachment-0001.html>
- Previous message (by thread): [Python-Dev] PEP 579 and PEP 580: refactoring C functions and methods
- Next message (by thread): [Python-Dev] Request for review
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list