Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!samsung!crackers!m2c!umvlsi!umaecs!amh!mbabramowicz
From: mbabramowicz@amherst.bitnet
Newsgroups: comp.sys.mac.programmer
Subject: Bug in Lightspeed Pascal 2.03
Message-ID: <11749.27a0a4c2@amherst.bitnet>
Date: 25 Jan 91 21:36:02 GMT
Lines: 27

I've encountered a really weird bug in Lightspeed Pascal 2.03, I think.
I was able to get around it, and for all I know it may have been corrected
in later versions, but I thought I'd mention it anyway.

Basically, the line:
   rndEndBeep := not rndEndBeep
failed to work.
That is, before the line was executed (I put a stop on it and watched the
variable via LightsBug), the value was TRUE. After the line executed, the
value was still TRUE. This happened a number of times without working succ-
essfully. Incidentally, rndEndBeep is a boolean variable (of course), and
I had several other similar statements that worked fine. Some of these were
even in the same "case" construct.

You're probably skeptical right now that I didn't do something stupid.
But I'm quite sure it is a bug, first of all, because debugging it, I was
able to see that the line executed but did not change the variable. 
Secondly, when I changed a variable declaration so that two boolean var-
iables listed separately were listed together 
soundOn, rndEndBeep : BOOLEAN;
then my program worked fine.

Weird... has anyone else had this happen? Does Symantec know about this?
Has it been fixed in LSP 3.0? I ask these questions out of curiousity only,
since it no longer affects me.

Michael Abramowicz