summaryrefslogtreecommitdiff
path: root/gcc/README.TRAD
diff options
context:
space:
mode:
authorroland <roland@138bc75d-0d04-0410-961f-82ee72b054a4>1992-05-28 20:30:28 +0000
committerroland <roland@138bc75d-0d04-0410-961f-82ee72b054a4>1992-05-28 20:30:28 +0000
commite5c4f55817353b41230fc04a99633f08974bf5ad (patch)
treed9848e0b84a49f58880da0a4612477897188a9b8 /gcc/README.TRAD
parent72cfdd818a5a2576465fb24f2be304a3c8efd027 (diff)
downloadgcc-e5c4f55817353b41230fc04a99633f08974bf5ad.tar.gz
entered into RCS
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@1116 138bc75d-0d04-0410-961f-82ee72b054a4
Diffstat (limited to 'gcc/README.TRAD')
-rw-r--r--gcc/README.TRAD55
1 files changed, 55 insertions, 0 deletions
diff --git a/gcc/README.TRAD b/gcc/README.TRAD
new file mode 100644
index 00000000000..07ccd16437b
--- /dev/null
+++ b/gcc/README.TRAD
@@ -0,0 +1,55 @@
+This is a partial list of how `gcc -traditional' disagrees with
+traditional C compilers (perhaps only some of them). Most of these
+differences are not bugs.
+
+---------------------------------------------------------------------------
+K&R-1 (2.4.3) says:
+
+ "If the character following a backslash is not one of those
+ specified {in the table above}, the backslash is ignored."
+
+Up until recently, `gcc -traditional' complained about \x \a and \v
+appearing in a character or string literal. I believe however that
+this non-feature has been eliminated (recently).
+
+---------------------------------------------------------------------------
+When in -traditional mode, gcc allows the following erroneous pair of
+declarations to appear together in a given scope:
+
+ typedef int foo;
+ typedef foo foo;
+
+---------------------------------------------------------------------------
+K&R-1 (8.5) says:
+
+ "No field may be wider than a word."
+
+Gcc however allows:
+
+ struct S { int i:33; };
+
+---------------------------------------------------------------------------
+In K&R-1 there is no restriction against comments crossing include file
+boundaries. Gcc however doesn't allow this, even when in -traditional mode.
+
+---------------------------------------------------------------------------
+Regarding the length of identifiers, K&R-1 (2.2) says:
+
+ "No more than the first eight characters are significant,
+ although more may be used."
+
+Gcc treats all characters of identifiers as significant, even when in
+-traditional mode.
+
+---------------------------------------------------------------------------
+K&R-1 (2.2) says:
+
+ "An identifier is a sequence of letters and digits; the first
+ character must be a letter. The underscore _ counts as a letter."
+
+Gcc also allows dollar signs in identifiers. (This may also be an issue
+for the -pedantic option.)
+
+---------------------------------------------------------------------------
+
+