Hi Mira:

From mira@ccs.neu.edu Tue Dec  2 18:07:52 1997
--------- cut here --------

-- Organization of AP programs in packages

        - .vis files:
          + generic.vis -- for most generic visitors
          + xyz.vis -- for domain specific visitors.
         These also include generic modifies statements
         to give a name to generic combinations of the
         visitors.
Yes.

        - instantiation of visitors and startegies for
          a particular class graph in .beh. Also includes
          specific modifies statements.

Yes, the *.beh files become the glue files.

        - .st files for strategy types ????
Yes, I think that is a good idea.
Maybe, *.str. Kedar and I also talked about this. AP Studio
generates and visualizes and maintains *.cd and *.str files.

Doug does this fit into the rest of Demeter/Java?

        - where do we put the class dictionaries for the 
          objects declared by visitors?

           + it would be desirable to put them in 
             separated files, e.g.  generic.cd, xyz.cd       
           + conflicts between definitions in different .cd files?         
           + there shouldn't be conflicts if each .vis file "gets" the   
             structure information in its "own" .cd file
 
I was thinking that the temporary cd information should be in the .vis
file.

A typical single cd Demeter/Java program would then contain:

path-set1.str // class graph abstractions
path-set2.str
...
comp1.vis // the "new visitors": reusable building blocks
comp2.vis
...
task1.beh
task2.beh
...
application.cd

The *.beh files should probably explicitly import the required .str
and .vis files to allow to build libraries.


-- Karl