Sender: nate AT cartsys DOT com
Message-ID: <36310D20.CE9344A0@cartsys.com>
Date: Fri, 23 Oct 1998 16:11:28 -0700
From: Nate Eldredge <nate AT cartsys DOT com>
X-Mailer: Mozilla 4.05 [en] (X11; I; Linux 2.0.35 i486)
MIME-Version: 1.0
To: djgpp AT delorie DOT com
Subject: Re: Parse errors
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>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp AT delorie DOT com

Donn Miller wrote:

> It could mean that you've got a piece of hardware like memory or cache
> gone bad.  But with bad memory, you get parse errors in random places each
> time.  Like if the compiler tells you you forgot a semicolon somewhere,
> and there is one, you can be sure it's bad memory.

Not necessarily true.  There are certainly other possible explanations.

* Accidentally compiling the wrong file.  (This *does* happen!)
* Strange syntax error that manifests itself in unexpected ways
* Compiler bug

-- 

Nate Eldredge
nate AT cartsys DOT com