Pushed as obivous since this is GCC's coding conventions. -- >8 -- Change all occurrences of "Objective C" and "Objective C++" to "Objective-C" and "Objective-C++".
Except for the incorrect spelling example in the Coding Conventions page. Signed-off-by: Pietro Monteiro <[email protected]> --- htdocs/frontends.html | 2 +- htdocs/gcc-3.0/caveats.html | 2 +- htdocs/gcc-3.0/features.html | 2 +- htdocs/news.html | 8 ++++---- htdocs/projects/cpplib.html | 4 ++-- htdocs/projects/gupc.html | 2 +- 6 files changed, 10 insertions(+), 10 deletions(-) diff --git a/htdocs/frontends.html b/htdocs/frontends.html index 5a4ec767..53802749 100644 --- a/htdocs/frontends.html +++ b/htdocs/frontends.html @@ -11,7 +11,7 @@ <h1>GCC Front Ends</h1> <p>Currently the main GCC distribution contains front ends for C, C++, -Objective C, Objective C++, Fortran, Ada, Go, D, Modula-2, Rust, and +Objective-C, Objective-C++, Fortran, Ada, Go, D, Modula-2, Rust, and Cobol.</p> <p>There are several more front ends for different languages that have diff --git a/htdocs/gcc-3.0/caveats.html b/htdocs/gcc-3.0/caveats.html index 1bc91242..71be9446 100644 --- a/htdocs/gcc-3.0/caveats.html +++ b/htdocs/gcc-3.0/caveats.html @@ -30,7 +30,7 @@ semicolon) after the label.</li> <li>The poorly documented extension that allowed string constants in - C, C++ and Objective C to contain unescaped newlines has been + C, C++ and Objective-C to contain unescaped newlines has been deprecated and may be removed in a future version. Programs using this extension may be fixed in several ways: the bare newline may be replaced by <code>\n</code>, or preceded by <code>\n\</code>, or diff --git a/htdocs/gcc-3.0/features.html b/htdocs/gcc-3.0/features.html index 64449333..5d5bdef2 100644 --- a/htdocs/gcc-3.0/features.html +++ b/htdocs/gcc-3.0/features.html @@ -109,7 +109,7 @@ ISO C++ standard.</li> <li>New <a href="../news/inlining.html">inliner for C++</a>.</li> <li>Rewritten C preprocessor, integrated into the C, C++ and - Objective C compilers, with very many improvements including + Objective-C compilers, with very many improvements including ISO C99 support and <a href="../news/dependencies.html">improvements to dependency generation</a>.</li> diff --git a/htdocs/news.html b/htdocs/news.html index efefc1be..d6a471de 100644 --- a/htdocs/news.html +++ b/htdocs/news.html @@ -1451,7 +1451,7 @@ architecture. <dt><b>November 26, 2000</b></dt> <dd> -The C, C++ and Objective C front ends now use the integrated +The C, C++ and Objective-C front ends now use the integrated preprocessor exclusively; their independent ability to tokenize an input stream has been removed. </dd> @@ -1510,7 +1510,7 @@ version.)</li> <dt><b>November 2, 2000</b></dt> <dd> -The C, C++ and Objective C front ends to GCC now use an integrated +The C, C++ and Objective-C front ends to GCC now use an integrated preprocessor by default. If all goes well, this will also be the default mode for GCC 3.0. </dd> @@ -1534,7 +1534,7 @@ name for our development branch that will eventually become GCC 3.0. <dt><b>Sep 11, 2000</b></dt> <dd> Zack Weinberg of Cygnus, a Red Hat company, has contributed -modifications to the C, C++, and Objective C compilers which permit +modifications to the C, C++, and Objective-C compilers which permit them to use the C preprocessor library (cpplib) directly instead of via a separate executable. @@ -1553,7 +1553,7 @@ preprocessor. The lexer makes a single pass over the source files, whereas previously it made two. The macro expander operates on lexical tokens instead of text strings. -<p>ISO C, C++, and Objective C use the new preprocessor. Traditional +<p>ISO C, C++, and Objective-C use the new preprocessor. Traditional (K+R) C, Fortran, and Chill use an older implementation (taken from GCC 1) which obeys the rules for pre-standard C preprocessing. Either version may be used to preprocess assembly language.</p> diff --git a/htdocs/projects/cpplib.html b/htdocs/projects/cpplib.html index bc43b6c1..12e4532d 100644 --- a/htdocs/projects/cpplib.html +++ b/htdocs/projects/cpplib.html @@ -14,7 +14,7 @@ <p>cpplib has largely been completed, and is stable at this point. For GCC versions 3.0 and later, it is linked into the C, C++ and -Objective C front ends. Most future work will relate to character set +Objective-C front ends. Most future work will relate to character set issues, performance enhancements and improving cpplib as a stand-alone library.</p> @@ -70,7 +70,7 @@ after thought, which is not entirely coincidental.</p> codes, there would be no need for a translation layer between the codes returned by cpplib and the codes used by the parser. Noises have been made about a recursive-descent parser that - could handle all of C, C++, Objective C; if this ever happens, + could handle all of C, C++, Objective-C; if this ever happens, it should use cpplib's token codes.</li> <li>String concatenation should be handled in the function diff --git a/htdocs/projects/gupc.html b/htdocs/projects/gupc.html index e38cd240..20bb5f3b 100644 --- a/htdocs/projects/gupc.html +++ b/htdocs/projects/gupc.html @@ -19,7 +19,7 @@ programs written in the <a href="https://github.com/Intrepid/GUPC";>UPC (Unified Parallel C)</a> language. The GNU UPC compiler extends the capabilities of GCC. The GUPC compiler is implemented as a C Language dialect translator, in -a fashion similar to the implementation of the GNU Objective C compiler. +a fashion similar to the implementation of the GNU Objective-C compiler. </p> <h2>Project Goal</h2> -- 2.43.0
