One class per file?
bdesth.quelquechose at free.quelquepart.fr
Sun Oct 5 16:30:51 CEST 2008
greg a écrit :
> Bruno Desthuilliers wrote:
>> Nope. But IIRC, one-class-per-file helps saving on compile/link time.
>> A problem we don't have with dynamic languages !-)
> That's mostly true. Although I've noticed that if I have
> a very large .py file, it can take a noticeable number
> of moments to regenerate the .pyc after I've changed
Indeed - and "very large" files are a maintainance nightmare anyway.
The point was that with C++, when you edit a file, you not only have to
recompile this file, you *also* have to relink *everything* depending on
what's defined in this file. So the saving is mostly on on (re)linking
More information about the Python-list