Date:	Sun, 10 Aug 1997 18:07:36 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To:	Lyle <lpak1 AT ccds DOT cc DOT monash DOT edu>
cc:	djgpp AT delorie DOT com
Subject:	Re: Parse Error Before '*'
In-Reply-To:	<33EC081E.F3E7C86C@NO_SPAMccds.cc.monash.edu>
Message-ID:	<Pine.SUN.3.91.970810180656.4651g-100000@is>
MIME-Version:	1.0

On Sat, 9 Aug 1997, Lyle wrote:

> which i had in Borland Turbo C++ V3.0. When i compile in BTC++ i get no
> warnings, no errors. Now i try compile and i am getting a "parser error
> before '*'" in a lot of my header files (then of course nothing
> compiles).

``Parse error'' in GCC's parlance means ``syntax error''.  You need to
look at or near the lines whose numbers GCC prints and find out why
does the compiler think this syntax is incorrect.

By far the most frequent cause of these messages is that you use a
typedef, but GCC doesn't see it.  Consider this:

	 extern frob_t * my_variable;

If GCC doesn't see the definition of `frob_t' type (possibly because
you haven't included the header with that definition), you'll get the
dreaded ``parse error''.

Btw, it helps to include a few lines where GCC complains in your
messages.

- Raw text -