From:	ao950 AT FreeNet DOT Carleton DOT CA (Paul Derbyshire)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Parse Error Before '*'
Date:	11 Aug 1997 07:42:20 GMT
Organization:	The National Capital FreeNet
Lines:	20
Message-ID:	<5smfos$5sn@freenet-news.carleton.ca>
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 970810180656 DOT 4651g-100000 AT is>
Reply-To:	ao950 AT FreeNet DOT Carleton DOT CA (Paul Derbyshire)
NNTP-Posting-Host:	freenet3.carleton.ca
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

Yep. A parse error before * is usually a typedef not recognized, or else
a typo.

Four possibilities come to mind:

1. The compiler it was ported from allowed bool in regular C, whereas DJGPP
   only has bool in C++. (This doesn't seem likely but there are some weird
   compilers out there!)
2. The compiler typedef'd unsigned int uint, or unsigned short ushort, or
   one of those, automatically. GCC does not.
3. You forgot a #include.
4. The other compiler had a typedef in a header that GCC has in a
   different header. This is unlikely in an ansi standard header, but
   DOS-specific headers might do this.
--
    .*.  Where feelings are concerned, answers are rarely simple [GeneDeWeese]
 -()  <  When I go to the theater, I always go straight to the "bag and mix"
    `*'  bulk candy section...because variety is the spice of life... [me]
Paul Derbyshire ao950 AT freenet DOT carleton DOT ca, http://chat.carleton.ca/~pderbysh

- Raw text -