From:	silkwodj AT my-dejanews DOT com
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Parse errors
Date:	Tue, 27 Oct 1998 15:17:50 GMT
Organization:	Deja News - The Leader in Internet Discussion
Lines:	14
Message-ID:	<714o6t$jej$1@nnrp1.dejanews.com>
References:	<4af57b8d DOT 36227988 AT aol DOT com> <Pine DOT OSF DOT 4 DOT 05 DOT 9810122353150 DOT 5384-100000 AT sable DOT ox DOT ac DOT uk> <703q7p$bus$1 AT nnrp1 DOT dejanews DOT com> <Pine DOT BSF DOT 4 DOT 05 DOT 9810230201470 DOT 22326-100000 AT localhost> <36310D20 DOT CE9344A0 AT cartsys DOT com>
NNTP-Posting-Host:	205.147.228.2
X-Article-Creation-Date:	Tue Oct 27 15:17:50 1998 GMT
X-Http-User-Agent:	Mozilla/4.0 (compatible; MSIE 4.01; Windows 95)
X-Http-Proxy:	1.0 x11.dejanews.com:80 (Squid/1.1.22) for client 205.147.228.2
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Memory errors cause a lot of other problems that are hard not to notice.  I
had this kind of problem once and it was like having a virus.  Large
executables that were copied to zip drives were wrecked just as I thought I
was archiving.

Well, anyway my original parse errors were eventually found.  George's advice
regarding the addition of the assumed to be missing brace in advanced
positions through the code worked.  Actually, the missing brace was found in
a header file.	You know, extern "C" { function1(); function2(); etc.  wasn't
closed. The tip off should have been the sudden appearance of the same error
in a related but otherwise untouched module.

-----------== Posted via Deja News, The Discussion Network ==----------
http://www.dejanews.com/       Search, Read, Discuss, or Start Your Own    

- Raw text -