From: Lyle Newsgroups: comp.os.msdos.djgpp Subject: Re: Parse Error Before '*' Date: Fri, 15 Aug 1997 13:27:51 +1000 Organization: Monash Uni Lines: 37 Message-ID: <33F3CCB7.4AF15472@NO_SPAMccds.cc.monash.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: ascend-1-06.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 john Latala wrote: > > ao950 AT FreeNet DOT Carleton DOT CA (Paul Derbyshire) writes: > > >I'll even write it for you: > > >2678194.67287474.12 Q: Porting a program to DJGPP, I get a heckuva lot of > > "parse error before '*'" messages. It compiles fine > > in WhizC 7.9! > > A: It's one of these: > > 1. 'far' and 'near' pointers. Search-and-replace all > > 'far *' and 'near *' to just '*'. > > Instead of going through all the source to replace far*/near* with * I think > it would be better to use a header which defines 'far' and 'near' as nothing. > > That way they disappear but if you ever have to port the code back to an > intel compiler you just remove the near/far redefinition ... > -- > john DOT Latala AT Waterloo DOT NCR DOT COM > > SYSTEM-E-ARMAGEDDON, WORLD quanta expired. System being shutdown. > SYSTEM-I-ARMAGEDDON, Have a nice day. Hi, Thats a really cool soloution! thanks... -- 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/ | \/ | `----'