When reading the documentation
|
there is a node in the tree. Also every node has a `src` attribute to point at the exact location in the source file |
|
where every node originated. |
|
* You can use handy pattern matching primitives like constructor matching, list matching and deep matching for fast analysis. |
|
* `src` and `decl` fields on AST nodes correspond to the M3 Core model's `declarations` and `uses` relations, and others. Combining |
|
AST analysis with lookups in an M3 core model is usually very handy. |
I got confused in multiple ways.
-
Does the src field correspond to declarations or uses (respectively is missing)?
And how should I interpret "and others"? Are there additional relations in src? If so, which?
-
Every AST node has a src attribute to point at the exact location in the source file where every node originated
AND
src field on AST correspond to a relation in the M3 Core model.
Aren't attribute and field synonyms?
When reading the documentation
java-air/src/lang/java/m3/AST.rsc
Lines 37 to 41 in 8818a88
I got confused in multiple ways.
Does the
srcfield correspond todeclarationsoruses(respectively is missing)?And how should I interpret "and others"? Are there additional relations in
src? If so, which?Every AST node has a
srcattribute to point at the exact location in the source file where every node originatedAND
srcfield on AST correspond to a relation in the M3 Core model.Aren't attribute and field synonyms?