Article View: comp.sys.amiga.tech
Article #9823Re: Bug in Manx C
From: Mark Jones
Date: Fri, 16 Sep 1988 15:59
Date: Fri, 16 Sep 1988 15:59
11 lines
902 bytes
902 bytes
In article <3111@utastro.UUCP>, sjk@utastro.UUCP (Scot Kleinman) writes: > > I think I have a uncovered a bug in my version of Aztec C 3.60a. > I'm in a function, have just set a variable I am going to return, but am > entering a for loop that modifies some other variables. At the end of the > for loop, my original variable (the one I first set and am going to return) > has been changed. I put a printf in the loop and found that the change occurs > only on the last loop iteration. I would include the code, Please include the code, this sounds a lot like a subscript out of range problem.
Technical Details
Message-ID:
<2572@ingr.UUCP>Path:
arc1-ca.pugleaf.net!utzoo!attcan!uunet!ingr!jonesReferences:
<3111@utastro.UUCP>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!ingr!jones From: jones@ingr.UUCP (Mark Jones) Newsgroups: comp.sys.amiga.tech Subject: Re: Bug in Manx C Message-ID: <2572@ingr.UUCP> Date: 16 Sep 88 15:59:35 GMT References: <3111@utastro.UUCP> Organization: Intergraph Corp. Huntsville, Al Lines: 11