head	1.1;
access;
symbols
	gcc-2_8_1-990325:1.1
	gcc-2_8_1-990319:1.1
	gcc-2_8_1-990302:1.1
	gcc_2_8_1-990302:1.1
	gcc_2_8_1-990222:1.1
	gcc-2_8_1-990109:1.1
	gcc-2_8_1-981210:1.1
	gcc-2_8_1-981208:1.1
	gcc-2_8_1-980929:1.1
	gcc_2_8_1-980929:1.1
	gcc-2_8_1-980928:1.1
	gcc-2_8_1-980813:1.1
	gcc-2_8_1-980811:1.1
	gcc-2_8_1-980718:1.1
	gcc-2_8_1-980705:1.1
	gcc-2_8_1-980627:1.1
	gcc-2_8_1-980609:1.1
	gcc-2_8_1-980608:1.1
	gcc-2_8_1-980529:1.1
	gcc-2_8_1-980525:1.1
	gcc-2_8_1-980513:1.1
	gcc-2_8_1-980502:1.1
	gcc-2_8_1-980402:1.1
	gcc-2_8_1-980426:1.1
	gcc-2_8_1-980419:1.1
	gcc-2_8_1-980413:1.1
	gcc-2_8_1-980412:1.1
	gcc-2_8_1-980407:1.1
	gcc-2_8_1-980401:1.1
	gcc_2_8_1-980315:1.1
	gcc-2_8_1-RELEASE:1.1;
locks; strict;
comment	@# @;


1.1
date	92.05.28.20.30.28;	author roland;	state Exp;
branches;
next	;


desc
@This is a partial list of how `gcc -traditional' disagrees with
@


1.1
log
@entered into RCS
@
text
@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.)

---------------------------------------------------------------------------


@
