Path: utzoo!utgpu!watmath!att!dptg!rutgers!gatech!prism!vsserv!geomag!prem
From: prem@geomag.fsu.edu (Prem Subrahmanyam)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Lattice C 5.02 BUGS
Keywords: Here's another one for your viewing pleasure
Message-ID: <142@vsserv.scri.fsu.edu>
Date: 30 Aug 89 19:10:48 GMT
References: <2023@softway.oz>
Sender: news@vsserv.scri.fsu.edu
Reply-To: prem@geomag.gly.fsu.edu (Prem Subrahmanyam)
Organization: Florida State University Computing Center
Lines: 33


    This is a serious bug I've discovered while working with 
    DBW_Render.  The two following statements should be the same,
    right?

    for (i=0; i < something; i++)
	/* insert command to loop here */ ;

    for (i=0; i < something; i++) {
	/* same command as before */ ;
	}

    the only difference is that the second statement has a begin and end
    bracket, while the first one does not.  Albeit, this is not impossible
    to work around, but it sure makes it a pain to work on any program 
    written for any other compiler 'cept Lattice.  By the way, the second
    statement always works properly, while the first one is sort of hit
    and miss, sometimes they work, sometimes not.  I have spent 2 whole
    weeks trying to fix the marble texture in DBW due to just this problem.
    I would not have guessed such a basic bug would be there causing problems...
    so I would go looking at every function and dumping all kinds of values.
    All I did to make it work was to insert the braces in place and voila.
    
    I'm not at all saying that I don't like the Lattice environment.  I really
    like  LSE, the addition of Conman, PopCLI, etc, and I really like the
    product, however, it seems that there are a lot of problems due to
    incomplete testing prior to release.  I hope that fixes for this very
    trivial bug will be quickly forthcoming, as I have planned on porting
    C programs written in a UNIX environment and don't want to have to go
    rooting through the code for all the for() statements and put begin/end
    braces after each one.  This should not be for what claims to be an ANSI
    compatible compiler!!!!!
    ---Prem Subrahmanyam (prem@geomag.gly.fsu.edu)