Re: Re: software design clarification

[email protected] (Gilles J. Seguin) Tue, 01 May 2007 12:55:03 -0400
Newsgroups gmane.comp.documentation.synopsis
Message-ID <[email protected]>
On Mon, 2007-04-30 at 19:00 +0200, Markus Elfring wrote:
> > Are you asking about the development process or the resulting design & implementation?
> >   
> 
> Both. Can UML drawings show the open design details that are general to 
> our discussion?
> How do you think about consider interesting relationships without the 
> selected programming languages?
> 
> 
> >> Are the interfaces "XQuery" or "QVT" on your wish list in this context?
> >>     
> >
> > No.
> 
> I imagine that there are approaches where we can benefit from XML queries.
> - Superx++
> - o:XML
> - srcML
> - GCC XML Node Introspector
> - GXL: Paper "Towards a Standard Schema for C/C++"

Read introduction to XML.
XML is an utility to allow communication between disparate tools.
That is,
             +--------+ 
inp_file --> | parser | --> new_file_1
             +--------+

               +--------+
new_file_1 --> |   IL   | --> new_file_2
               +--------+

where IL is Intermediate Language or Representation
      new_file_1 is flat file or XML representation
      new_file_2 is flat file or XML representation

For the moment we are very anxious to have the parser working.

I have flat file representation of new_file_1 that even not requires
the use of diagram, means still enough simple to be brain process.
Though diagram is necessary for exchange of information with
other programmers or new comer.

new_file_1 is desired for
- code generation modification like instrumentation, ...
- language extensions utilities
- header files inclusion analysis

new_file_2 can be used for
- inter-language wrapper.
- call trees generation
- hierarchical class analysis