Why NOT only one class per file?

Sherm Pendley spamtrap at dot-app.org
Thu Apr 5 03:13:25 CEST 2007


Bruno Desthuilliers <bdesth.quelquechose at free.quelquepart.fr> writes:

> Chris Lasher a écrit :
>
>> so I thought I'd ask here to
>> see why the Python idiom is the way it is: why should we NOT be
>> placing classes in their own separate files?
>
> Because it just sucks.

...

> Just ask him why Java insists on 'one-(public)-class-per-file', and
> why it's considered good form in C++. I mean, the real *technical*
> reasons...

Yeah, as if "because it just sucks" is a technical reason. :-)

It's a stylistic thing, nothing more. There's no technical basis for it,
just personal preference.

sherm--

-- 
Web Hosting by West Virginians, for West Virginians: http://wv-www.net
Cocoa programming in Perl: http://camelbones.sourceforge.net



More information about the Python-list mailing list