[Python-Dev] .clinic.c vs .c.clinic
Meador Inge
meadori at gmail.com
Mon Jan 20 15:35:09 CET 2014
More information about the Python-Dev mailing list
Mon Jan 20 15:35:09 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 Mon, Jan 20, 2014 at 2:05 AM, Larry Hastings <larry at hastings.org> wrote: Contestant 1: "Add .clinic.h" > > foo.c -> foo.c.clinic.h > foo.h -> foo.h.clinic.h > > -0 > Contestant 2: "Add .ac.h" > > foo.c -> foo.c.ac.h > foo.h -> foo.h.ac.h > > -1 > Contestant 3: "Add .clinic" > > foo.c -> foo.c.clinic > foo.h -> foo.h.clinic > > -1 (This will break too many tools in the C/C++ tools ecosystem and I am not convinced by any of the arguments given those far.) > Contestant 4: "Put in clinic directory, add .h" > > foo.c -> clinic/foo.c.h > foo.h -> clinic/foo.h.h > > +1 > Contestant 5: "Put in __clinic__ directory, add .h" > > foo.c -> __clinic__/foo.c.h > foo.h -> __clinic__/foo.h.h > > -1 ("clinic" without the dunders more clear for a directory name.) -- Meador -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20140120/17698123/attachment.html>
- 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 ]
More information about the Python-Dev mailing list