Subj : Re: "File Scope" objects
To   : comp.programming,comp.software-eng
From : Phlip
Date : Fri Aug 26 2005 08:16 pm

Chris Sonnack wrote:

>> Give everything the most restricted scope possible.
>
> Absolutely.  And when several functions in one module share the
> same datum?

Then the most restricted scope possible is ... the module?

>> The book /Large Scale C++ Software Design/ reveals how we should
>> prefer the leanest possible .h files,...
>
> I very much agree.  Much easier to examine what a class does when
> you only have to look at its public interface.

The book is about _physical_ construction rules. Your compiler also likes to 
only see what it needs in .h files.

>> ...including by creating private functions inside .cpp files.
>> Private classes are an extension of this concept.
>
> Which are a form of file scoped object, so I take it you are in
> favor of such things?

Modulo community agreements, yes!

>> Design is about enabling changes,...
>
> That's ONE of the things it's about.

If everything else it's about got there via change, then...

-- 
  Phlip
  http://www.greencheese.org/ZeekLand  <-- NOT a blog!!!

.