Inheritance and Inner/Nested Classes

[Paul Morrow]

Peter Hansen wrote:

> The objects that are being parameterized (the ones the developer
> supplies) are not the same thing as the parameterization objects.

I'm not quite sure what you mean by "parameterization objects" as 
opposed to what the developer creates.  Note that there are two kinds of 
developers here: one that works on the Framework; and one that builds 
applications using the Framework.  It's the later that I've been talking 
about.

For each application, the application developer creates an object that 
describes the application. This object contains a bunch of settings that 
customize the Framework.  For any given app, there are a lot of possible 
settings, where the settings can be grouped into a number of categories 
(security, style, structure, content, etc.).  I could just say that the 
namespace inside of the object (the app developer supplies) is flat, but 
that would get messy fast.  It seems that it would be better to store 
related attributes together in their own namespace inside of the object. 
That's what I imagined using the inner classes for.