From f69d06e4025acf5d0880e88aa66c4e4280140feb Mon Sep 17 00:00:00 2001 From: Faisal Vali Date: Sat, 22 Jul 2017 12:04:37 +0000 Subject: [PATCH] [NFC, documentation] Prefer the term expansion instead of macro instantiation ... in the few remaining places where this was not corrected. git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@308823 91177308-0d34-0410-b5e6-96231b3b80d8 --- docs/InternalsManual.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/InternalsManual.rst b/docs/InternalsManual.rst index dc89d123c0..61875297e3 100644 --- a/docs/InternalsManual.rst +++ b/docs/InternalsManual.rst @@ -493,11 +493,11 @@ source code of the program. Important design points include: In practice, the ``SourceLocation`` works together with the ``SourceManager`` class to encode two pieces of information about a location: its spelling -location and its instantiation location. For most tokens, these will be the +location and its expansion 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). +expansion point or the location of the ``_Pragma`` itself). 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 die. -- 2.50.1