diff options
| author | Sandra Loosemore <sandra@codesourcery.com> | 2017-02-11 19:57:21 -0500 |
|---|---|---|
| committer | Sandra Loosemore <sandra@gcc.gnu.org> | 2017-02-11 19:57:21 -0500 |
| commit | 95bbcf58810306bb5f0c24e67620a9e710b0d691 (patch) | |
| tree | 9308f9e898f9a7c07db466fe610bec625578f1a1 /gcc/doc/cppinternals.texi | |
| parent | 7b65f47719b4dd60c63eca8f90e9821024b32fc6 (diff) | |
| download | gcc-95bbcf58810306bb5f0c24e67620a9e710b0d691.zip gcc-95bbcf58810306bb5f0c24e67620a9e710b0d691.tar.gz gcc-95bbcf58810306bb5f0c24e67620a9e710b0d691.tar.bz2 | |
cpp.texi: Replace "stringify"/"stringification" with C standard terminology...
2017-02-11 Sandra Loosemore <sandra@codesourcery.com>
gcc/
* doc/cpp.texi: Replace "stringify"/"stringification" with C
standard terminology "stringize"/"stringizing" throughout.
* doc/cppinternals.texi: Likewise.
From-SVN: r245371
Diffstat (limited to 'gcc/doc/cppinternals.texi')
| -rw-r--r-- | gcc/doc/cppinternals.texi | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/gcc/doc/cppinternals.texi b/gcc/doc/cppinternals.texi index e2259b0..94de21b 100644 --- a/gcc/doc/cppinternals.texi +++ b/gcc/doc/cppinternals.texi @@ -203,7 +203,7 @@ error about an unterminated macro argument list. The C standard also specifies that a new line in the middle of the arguments to a macro is treated as whitespace. This white space is -important in case the macro argument is stringified. The state variable +important in case the macro argument is stringized. The state variable @code{parsing_args} is nonzero when the preprocessor is collecting the arguments to a macro call. It is set to 1 when looking for the opening parenthesis to a function-like macro, and 2 when collecting the actual @@ -374,7 +374,7 @@ the pointers to the tokens of its expansion that are returned will always remain valid. However, macros are a little trickier than that, since they give rise to three sources of fresh tokens. They are the built-in macros like @code{__LINE__}, and the @samp{#} and @samp{##} operators -for stringification and token pasting. I handled this by allocating +for stringizing and token pasting. I handled this by allocating space for these tokens from the lexer's token run chain. This means they automatically receive the same lifetime guarantees as lexed tokens, and we don't need to concern ourselves with freeing them. @@ -478,7 +478,7 @@ ways. I strongly recommend you have a good grasp of how the C and C++ standards require macros to be expanded before diving into this section, let alone the code!. If you don't have a clear mental -picture of how things like nested macro expansion, stringification and +picture of how things like nested macro expansion, stringizing and token pasting are supposed to work, damage to your sanity can quickly result. @@ -744,7 +744,7 @@ We would then have it take its spacing from the first of these, which carries source token @samp{foo} with no leading space. It is vital that cpplib get spacing correct in these examples since any -of these macro expansions could be stringified, where spacing matters. +of these macro expansions could be stringized, where spacing matters. So, this demonstrates that not just entering macro and argument expansions, but leaving them requires special handling too. I made |