[Synopsis-devel] Re: software design clarification
Markus Elfring Markus.Elfring at web.deMon Apr 30 16:40:17 UTC 2007
- Previous message: [Synopsis-devel] Re: software design clarification
- Next message: [Synopsis-devel] Re: software design clarification
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
> Yes, the parse tree is provided by the Synopsis::PTree API (C++), > while the AST is provided by the Synopsis.AST API (Python). > Can it be that you mean abstract semantic graph with your "AST"? http://en.wikipedia.org/wiki/Abstract_syntax_tree#External_links Would you like to map the Python interface to C++ classes? The other conversion direction would be supported by the tool "Simplified Wrapper and Interface Generator" (http://www.swig.org/compare.html). > Not a class, but an object (a PTree::Node, representing the root node > of the tree). > I suggest to provide a higher level API for compilation units (source files) and project related attributes. > Not sure what you mean by 'mapping' in this context. The source from > which the parse tree is built may or may not be dependent on platform- > specific details (system headers, say), and so will the parse tree. > Header files can be part of platform independent standard specifications. The choice of an useable programming language can be a platform dependent aspect. > I still fail to see what you are aiming at. So far it sounds pretty academic. > I would like to stress the distinction of logical design and physical implementation. I hope that open issues can be better clarified with UML sketches. Regards, Markus
- Previous message: [Synopsis-devel] Re: software design clarification
- Next message: [Synopsis-devel] Re: software design clarification
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Synopsis-devel mailing list