[Python-Dev] .clinic.c vs .c.clinic (original) (raw)
Larry Hastings larry at hastings.org
Mon Jan 20 22:40:17 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 01/20/2014 05:03 AM, Nick Coghlan wrote:
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.
You're correct, I'm not talking about a top-level directory here. I'm talking about creating a "clinic" subdirectory in the same directory as the original file. The transformation suggested above was exact.
//arry/ -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20140120/b6413f8c/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 ]