Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!usc!wuarchive!udel!wack
From: wack@udel.edu (Andrew Wack)
Newsgroups: comp.sys.apple
Subject: Re: ORCA/C problems
Summary: This one is bizzare..
Message-ID: <11268@nigel.udel.EDU>
Date: 16 Feb 90 02:55:52 GMT
Sender: usenet@udel.EDU
Reply-To: wack@udel.edu (Andrew Wack)
Organization: University of Delaware
Lines: 39

After spending 6 frustrating hours trying to debug my program I came
upon another ORCA/C bug.  The problem was that after calling a certain
procedure from main, all my variable declared in main were trashed.
Actually, after making this procedure call, the memory locations that
the variables were stored in changed!!  I finally isolated the problem
to the following code fragment inside a while loop in the offending
procedure:

#define FLOOR(A,B) ((long)(A / B) * B)

      if (FLOOR(bs,512) <= (bl_current->length + bl_current->start) )
	 {
	 }

(the define is in for reference)

The problem goes away if I change the <= to <!!  The change doesn't affect
the results of the procedure since I just add 1 to the right hand side of
the inequallity to make it work.  The big question is WHY?

This is really getting quite agrivating..is there a list of known bugs
somewhere?  Does the beta compiler fix these bugs?  When I first bought
this package I was quite impressed....not any more.  This seems like a
pretty obvious bug to make it past testing (then again, so does the
optimize bug that I pointed out a week ago).

At the current rate I am progressing I could have coded this project
in assembly!!

There, I feel better now...any and all help with these problems will be
much appreciated (please, save my sanity).




--
--------------------------------------------------------------------------------
Andrew Wack                               Gravitation cannot be held responsible
Internet : wack@udel.edu           for people falling in love -- Albert Einstein