[Python-Dev] .clinic.c vs .c.clinic (original) (raw)
Zachary Ware zachary.ware+pydev at gmail.com
Sat Jan 18 19:29:43 CET 2014
- Previous message: [Python-Dev] .clinic.c vs .c.clinic
- Next message: [Python-Dev] .clinic.c vs .c.clinic
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sat, Jan 18, 2014 at 12:10 PM, Serhiy Storchaka <storchaka at gmail.com> wrote:
18.01.14 19:09, Antoine Pitrou написав(ла):
On Sat, 18 Jan 2014 18:06:06 +0100 Stefan Krah <stefan at bytereef.org> wrote:
I'd rather see memoryview.h than memoryview.clinic.c.
Or, if this collides with Include/*, one of the following: memoryviewfunc.h // public functions memoryviewif.h // public interface Objects/memoryview.clinic.h should be fine. All my objections against .clinic.c are applicable to .clinic.h as well.
Would it be of any help for the clinic files to live in their own separate directory? Say, instead of Objects/memoryview.clinic.c, Clinic/memoryview.clinic.c?
-- Zach
- Previous message: [Python-Dev] .clinic.c vs .c.clinic
- Next message: [Python-Dev] .clinic.c vs .c.clinic
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]