[Python-Dev] .clinic.c vs .c.clinic (original) (raw)
Serhiy Storchaka storchaka at gmail.com
Mon Jan 20 14:31:53 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 ]
20.01.14 15:03, Nick Coghlan написав(ла):
On 20 January 2014 21:14, Serhiy Storchaka <storchaka at gmail.com> wrote:
20.01.14 10:05, Larry Hastings написав(ла):
Contestant 4: "Put in clinic directory, add .h"
foo.c -> clinic/foo.c.h foo.h -> clinic/foo.h.h -1. (Generated files are located far from origins, directory name clutters the namespace of directory names). Larry's not talking about a top level directory here (at least I hope he isn't). This proposal would mean using "Objects/clinic", "Python/clinic", "Modules/clinic" as appropriate.
This means the appearance of directories with the common name "clinic" in random places of the source tree. Some special name ("clinic", ".clinic") looks slightly less confusing to me.
- 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 ]