From: "A. Sinan Unur" Newsgroups: comp.os.msdos.djgpp Subject: Re: Parse Error Before '*' Date: Thu, 14 Aug 1997 15:54:54 -0500 Organization: Cornell University Lines: 41 Sender: asu1 AT cornell DOT edu (Verified) Message-ID: <33F3709E.4F8E@cornell.edu> References: <33F03C65 DOT 70B76774 AT NO_SPAMccds DOT cc DOT monash DOT edu> <5sur85$3il AT freenet-news DOT carleton DOT ca> NNTP-Posting-Host: 128 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 Paul Derbyshire wrote: > > Lyle (lpak1 AT NO_SPAMccds DOT cc DOT monash DOT edu) writes: > > >> extern frob_t * my_var; > > > > 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. i remember telling Lyle, following his post where he said >> Now i try compile and i am getting a "parser >> error before '*'" in a lot of my header files (then of course >> nothing> compiles). I am to a lost as what i am doing wrong? I have >> read the FAQ and only found an extract saying " C++ comments not >> supported in C" My code is only C, not C++. Has anyone every >> experienced this problem and could advice me on how to rectify the >> situation. (lyle) that: >how about you show us some of the code that seems to be generating >these errors? (an alternative is to post these questions to >news:alt.mindreading.programmers.) most probably you have stuff like >NEAR and FAR sprinkled around, but i cannot tell without seeing the >offending code. (sinan) > > *groan!* Good God, that should have occurred to me too. One for the > FAQ Eli? I'll even write it for you: it is obvious that neither of you really look at the faq, because under chapter 17. Converting DOS Programs/Libraries to DJGPP, there is question 17.7 What should I do with those "near" and "far" declarations? which addresses this issue. so, check your faqs before you post claiming that something is not in the faq. -- Sinan