[cfe-commits] r104746 - /cfe/trunk/docs/InternalsManual.html
Nick Lewycky
nicholas at mxc.ca
Wed May 26 14:48:10 PDT 2010
Author: nicholas
Date: Wed May 26 16:48:10 2010
New Revision: 104746
URL: http://llvm.org/viewvc/llvm-project?rev=104746&view=rev
Log:
Grammar fix: s/it's/its/g in
"it's spelling location and it's instantiation location"
Modified:
cfe/trunk/docs/InternalsManual.html
Modified: cfe/trunk/docs/InternalsManual.html
URL: http://llvm.org/viewvc/llvm-project/cfe/trunk/docs/InternalsManual.html?rev=104746&r1=104745&r2=104746&view=diff
==============================================================================
--- cfe/trunk/docs/InternalsManual.html (original)
+++ cfe/trunk/docs/InternalsManual.html Wed May 26 16:48:10 2010
@@ -532,12 +532,12 @@
</ol>
<p>In practice, the SourceLocation works together with the SourceManager class
-to encode two pieces of information about a location: it's spelling location
-and it's instantiation 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
-location where the token was used (i.e. the macro instantiation point or the
-location of the _Pragma itself).</p>
+to encode two pieces of information about a location: its spelling location
+and its instantiation 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 location where the token was used (i.e. the macro instantiation point
+or the location of the _Pragma itself).</p>
<p>The Clang front-end inherently depends on the location of a token being
tracked correctly. If it is ever incorrect, the front-end may get confused and
More information about the cfe-commits
mailing list