From: Lyle <lpak1 AT NO_SPAMccds DOT cc DOT monash DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Parse Error Before '*'
Date: Tue, 12 Aug 1997 20:35:17 +1000
Organization: Monash Uni
Lines: 43
Message-ID: <33F03C65.70B76774@NO_SPAMccds.cc.monash.edu>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 970810180656 DOT 4651g-100000 AT is>
NNTP-Posting-Host: ascend-2-30.cc.monash.edu.au
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

Eli Zaretskii wrote:
> 
> 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.

hi,

yer, if i would have included the line i;m sure you would have all
laughed and guven me the answer in the a second - it was simply the
'far' word. 

thanks for the  reply

Lyle
-- 
NOTE: Remove The comment "NO_SPAM" To Reply via Email!

-------------------------------[ **NEW ADDRESS**
lpak1 AT ccds DOT cc DOT monash DOT edu DOT au]
" Hello Chevra Kadish, You Kill 'em, We Chill 'em "            .----,
						               | oO |
	HTTP://www-personal.monash.edu.au/~lpak1/              | \/ |
		                                               `----'