Why NOT only one class per file?

[Sherm Pendley]

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

> Sherm Pendley a écrit :
>> Bruno Desthuilliers <bdesth.quelquechose at free.quelquepart.fr> writes:
>>
>>
>>>Sherm Pendley a écrit :
>>>
>>>In my book, it's huge classes and methods that are usually a smell of
>>>a design problem.
>>
>>
>> Obviously we're reading different books.
>
> Obviously. But I didn't gain this knowledge from books.

Obviously, you have no sense of humor.

> FWIW, I'd be interested if you'd let us know about any book pretending
> that monster classes are good design !-)

You've already decided that "monster classes" are bad design, and that
anything conflicting with your belief is mere pretense. Why should I waste
my time debating when you've already made up your mind?

>> But that's OK - I'm not on a crusade to convince everyone to work my way.
>> If "one class per file" doesn't work well for you, don't write that way.
>> All I'm saying is, what works well for you isn't necessarily what works
>> well for everyone.
>
> It seems that it works well for almost anyone having some real-world
> experience with languages like Python.

I didn't say otherwise. You're arguing a false dichotomy; the fact that one
approach works well does not prove that others won't work equally well. I'm
not saying that your preferred style is wrong; I'm just saying that it's a
matter of preference, not a universal truth.

sherm--

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