aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChris Lattner <sabre@nondot.org>2009-01-16 07:00:50 +0000
committerChris Lattner <sabre@nondot.org>2009-01-16 07:00:50 +0000
commit18376ddf4d900f5e79deb40e43984df4f06e92d9 (patch)
treeeecb7a0a1e86b417a9d9cca56967c51aa49c316a
parentdf7c17a8d02fe09a3466786bae3e40fc3252687a (diff)
update for terminology change.
git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@62310 91177308-0d34-0410-b5e6-96231b3b80d8
-rw-r--r--docs/InternalsManual.html4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/InternalsManual.html b/docs/InternalsManual.html
index 9d21ca7cc7..3e41d90ab5 100644
--- a/docs/InternalsManual.html
+++ b/docs/InternalsManual.html
@@ -436,7 +436,7 @@ source code of the program. Important design points include:</p>
</ol>
<p>In practice, the SourceLocation works together with the SourceManager class
-to encode two pieces of information about a location: it's physical location
+to encode two pieces of information about a location: it's spelling location
and it's virtual location. For most tokens, these will be the same. However,
for a macro expansion (or tokens that came from a _Pragma directive) these will
describe the location of the characters corresponding to the token and the
@@ -453,7 +453,7 @@ from this.</p>
tracked correctly. If it is ever incorrect, the front-end may get confused and
die. The reason for this is that the notion of the 'spelling' of a Token in
Clang depends on being able to find the original input characters for the token.
-This concept maps directly to the "physical" location for the token.</p>
+This concept maps directly to the "spelling location" for the token.</p>
<!-- ======================================================================= -->
<h2 id="liblex">The Lexer and Preprocessor Library</h2>