A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from http://mail.python.org/pipermail/python-dev/2014-January/131870.html below:

[Python-Dev] .clinic.c vs .c.clinic

[Python-Dev] .clinic.c vs .c.clinic [Python-Dev] .clinic.c vs .c.clinicNick Coghlan ncoghlan at gmail.com
Mon Jan 20 14:03:16 CET 2014
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.

That's substantially *less* directory clutter rather than more, just
like __pycache__ vs the old model of implicitly creating adjacent .pyc
and .pyo files.

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4