[svn] 1063: ImplementationCompiler abstract syntax tree generation

Question

Revision: 1063
Author: [email protected]
Date: 2008-04-02 08:31:38 -0700 (Wed, 02 Apr 2008)
Log Message:
ImplementationCompiler abstract syntax tree generation
work-in-progress. Most of the methods for the equivalent Velocity
macros in ClassDef.vm and ClassDefLib.vm are stubbed out in
ImplementationGenerator. Note, with -generate-abstract-syntax-tree
set to true, mxml compilation is mostly broken. The current default
is false.
checkintests Passed: YES
Needs QA: Not yet
Needs DOC: NO
API Change: NO
Code-level description of changes:
swfutils/src/java/flash/swf/tools/SyntaxTreeDumper.java
Added evaluate() for BlockNode, CommentNode, TypeIdentifierNode,
and UsePragmaNode.
Modified evaluate() for CallExpressionNode, GetExpressionNode,
SetExpressionNode, and FunctionSignatureNode to include more info.
compiler/src/java/flex2/compiler/as3/AbstractSyntaxTreeUtil.java
Initial checkin.
compiler/src/java/flex2/compiler/as3/binding/DataBindingExtension.java
Moved numerous common methods to AbstractSyntaxTreeUtil.
compiler/src/java/flex2/compiler/mxml/rep/Model.java
Made getEffects() public.
compiler/src/java/flex2/compiler/mxml/rep/MxmlDocument.java
Added generics to getDeclarationIterator(), getImports(),
getScripts(), and getMetadata().
Added getInterfaceNames().
compiler/src/java/flex2/compiler/mxml/rep/DocumentInfo.java
Changed return type of getImportNames() from Collection to Set.
compiler/src/java/flex2/compiler/mxml/ImplementationCompiler.java
Modified parse1() to call generateImplementationAST() if
getGenerateAbstractSyntaxTree() is true. Otherwise,
generateImplementation() is called.
compiler/src/java/flex2/compiler/mxml/ImplementationGenerator.java
Initial checkin.
Modified Paths:
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/binding/DataBindingExtension. java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/ImplementationCompiler.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/rep/DocumentInfo.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/rep/Model.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/rep/MxmlDocument.java
flex/sdk/trunk/modules/swfutils/src/java/flash/swf/tools/SyntaxTreeDumper.java
Added Paths:
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/AbstractSyntaxTreeUtil.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/ImplementationGenerator.java

Answer 1

Hi Florian,
you can use the resource / EMF API directly in a plain (non-interactive)
environment.
If you want to enrich your model you should investigate using imported
metamodels and derived properties for the derivable information.
However, the Linker#afterModelLinked is usually a good place to enhance
the model.
Regards,
Sebastian
Need professional support for Eclipse Modeling?
Go visit: http://xtext.itemis.com
Am 29.11.10 19:39, schrieb Florian Gessner:
> Hi Sebastian,
>
> thanks for your fast reply.
> The example described in the blog uses the IDocumentEditor to manipulate
> the data. I do not want to implement this in the UI layer but in the
> backend.
> I think EMF should would independent from this, but for me it is not
> clear how I can integrate this into the backend. I think it would be a
> bit strange if I would enrich the model by some logic during validation
> or linking. Or is this how it works?
>
> Thanks and best regards
> Florian