Skip to main content
aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorDoug Schaefer2004-11-17 15:47:34 -0500
committerDoug Schaefer2004-11-17 15:47:34 -0500
commitcea83a5a77a3557bb3ba0352f4ee62eaa253b797 (patch)
tree3d684b9c0255a5feac693980d26f3862dd964800 /doc/org.eclipse.cdt.doc.isv
parent176c7265677179a23f56d08515beed62629ad5eb (diff)
downloadorg.eclipse.cdt-cea83a5a77a3557bb3ba0352f4ee62eaa253b797.tar.gz
org.eclipse.cdt-cea83a5a77a3557bb3ba0352f4ee62eaa253b797.tar.xz
org.eclipse.cdt-cea83a5a77a3557bb3ba0352f4ee62eaa253b797.zip
Updated DOM documentation.
Diffstat (limited to 'doc/org.eclipse.cdt.doc.isv')
-rw-r--r--doc/org.eclipse.cdt.doc.isv/guide/dom/index.html23
1 files changed, 18 insertions, 5 deletions
diff --git a/doc/org.eclipse.cdt.doc.isv/guide/dom/index.html b/doc/org.eclipse.cdt.doc.isv/guide/dom/index.html
index f36f840cd70..6e01dc4bb8b 100644
--- a/doc/org.eclipse.cdt.doc.isv/guide/dom/index.html
+++ b/doc/org.eclipse.cdt.doc.isv/guide/dom/index.html
@@ -14,16 +14,29 @@ for CDT 3.0. Changes should be expected until further notified.</span><br>
Model, is a programmatic way to see the underlying source code in both
a syntactic and semantic view using an Abstract Syntax Tree (AST) and
to allow changes in the AST to be reflected back out to the source
-code. Sounds simple enough, but with the complexity of the C and C++
-languages with an intermixing of pre-processor goodness, it certainly
-has it's challenges.<br>
+code.<br>
</p>
<h2>Syntactic View</h2>
-<p><br>
+<p>The syntactic view (which we sometimes call the physical view)
+represents the syntactic structure of the program. This is driven
+mainly by the grammar that the parser follows, mapping from terminals
+up to the entry rule in the grammer. This view fulfills the role of a
+traditional Abstract Syntax Tree, and you'll see that the classes that
+make up this view have AST in their name.<br>
</p>
<h2>Semantic View</h2>
+<p>The semantic view (which we sometimes call the logical view)
+represent semantic elements in the program. These elements are
+generally types, variables, and functions. The JDT calls these things
+bindings, so we do to. However, the more general rule is that anything
+that links sub-branches of the AST is a binding.<br>
+</p>
<h2>Workspace-Wide View</h2>
+<p>Once you have a binding, it is possible to find all translation
+units that declare or refer to that binding.</p>
<h2>Rewriting</h2>
-<br>
+<p>From the Syntactic view, you can ask the AST Rewriter to calculate
+the TextEdits required to accomplish changes to the AST.<br>
+</p>
</body>
</html>

Back to the top