Re: cppx

["Stephen Regan" <sregan@uci.edu>]

Hi Yuzo,

That's cool that you got it to work, even though the program had to be
altered.  The next thing I want to do is run some simple c++ classes that
use inheritance through cppx.  I have a few really small ones.  The io is
only in the driver program.  I can just remove the io from the driver.  It
would be interesting to have a graph (in gxl) that shows relationships
between classes.  And if I keep the header files down to a minimum, the gxl
file might be a reasonable size.  I might see if I can get cppx to find the
include directory, but on the other hand we don't really need that io stuff
in our gxl files anyway.  At this point, we just need some fairly simple
programs that can be extracted into gxl and visualized in various tools for
comparison.  Susan is considering the possibility of getting a Linux
machine.  We could put Swagkit on that.  Swagkit begins with cppx and
further "prepares" the facts.

>From the Swagkit web site:

The pipeline currently consists of 5 major steps:
  a.. cppx: Extract the facts. Produces *.ta from the original source files
  b.. prep: Prepare the facts. Produces *.o.ta from the extracted facts
  c.. linkplus: Link the facts. Produces out.ln.ta from *.o.ta
  d.. layoutplus: Layout the facts. Produces out.ls.ta from out.ln.ta
  e.. lsedit: Visualize the facts.

Some things worth noting about Swagkit:
It performs abstraction to the architectural level, which may mean that more
stuff will be removed than we would like.
Also, "A port to Solaris is possible, but not currently available."

I'll read up on Swagkit some more so we can decide if we want to set it up.
Susan suggested just downloading it and trying to run on Unix, in our
'sesweb/tools' directory.  I don't see why not.

Steve