From 390c5e2bb3551011f523246648d0c25d4ce4efb4 Mon Sep 17 00:00:00 2001
From: law <law@138bc75d-0d04-0410-961f-82ee72b054a4>
Date: Sun, 12 Jul 1998 00:25:49 +0000
Subject:         * g++.1 (-traditional): Remove duplicated documentation.

git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@21064 138bc75d-0d04-0410-961f-82ee72b054a4
---
 gcc/cp/g++.1 | 32 --------------------------------
 1 file changed, 32 deletions(-)

(limited to 'gcc/cp/g++.1')

diff --git a/gcc/cp/g++.1 b/gcc/cp/g++.1
index ae016fad082..5101d5fc1f6 100644
--- a/gcc/cp/g++.1
+++ b/gcc/cp/g++.1
@@ -430,38 +430,6 @@ differently depending on whether `\|\c
 testing both of these predefined macros you can distinguish four
 situations: GNU C, traditional GNU C, other ANSI C compilers, and
 other old C compilers.
-.TP
-\ \ \ \(bu
-In the preprocessor, comments convert to nothing at all, rather than
-to a space.  This allows traditional token concatenation.
-.TP
-\ \ \ \(bu
-In the preprocessor, macro arguments are recognized within string
-constants in a macro definition (and their values are stringified,
-though without additional quote marks, when they appear in such a
-context).  The preprocessor always considers a string constant to end
-at a newline.
-.TP
-\ \ \ \(bu
-The preprocessor does not predefine the macro \c
-.B __STDC__\c
-\& when you use
-`\|\c
-.B \-traditional\c
-\&\|', but still predefines\c
-.B __GNUC__\c
-\& (since the GNU extensions indicated by 
-.B __GNUC__\c
-\& are not affected by
-`\|\c
-.B \-traditional\c
-\&\|').  If you need to write header files that work
-differently depending on whether `\|\c
-.B \-traditional\c
-\&\|' is in use, by
-testing both of these predefined macros you can distinguish four
-situations: GNU C, traditional GNU C, other ANSI C compilers, and
-other old C compilers.
 .PP
 .TP
 \ \ \ \(bu
-- 
cgit v1.2.3