Modules merging support in ClassAnalyzer

[Alan Bateman]

Mandy Chung wrote:
> Mark, Alan,
>
> I have implemented the modules merging support in ClassAnalyzer.  The 
> syntax to specify the group module (i.e. enclosing module) for a 
> module is to prepend the group name to the module name separated by 
> ":" (i.e. <group name>:<module name>.  
Specifying the profile (or group, terminology???) in the module 
definition seems right and avoids needing to maintain a separate file. 
I'm okay with the syntax.

The suggestion to use the square brackets around the module name was 
just to make it a bit clear as the file is essentially split into 
section. I assume we'll be adding in "permits" and other things shortly 
and it might be neater to just drop the "=" delimiter.

Is the summary file the same as the modules.summary or does it list the 
modules that it includes? The complete class list for the profile/group 
will be needed by the build or tools so having a quick way to get to 
that would be good (can either be a full class list or the list of files 
to concatenate to get the full list).

-Alan.