Re: Is this a bug in 4GL 4.10?

In article <1992May20.030055.14552@informix.com> aland@informix.com (Colonel Panic) writes: >In article <1992May19.194914.4177@informix.com> craigbr@informix.com (Craig Browning) writes: >>In article <1992May18.204436.4282@mips.mitek.com> jmaddox@dbaix.oc.com (John Maddox) writes: >> >>>Thought I'd bounce this question around the net and see what comments >>>it generates..... >>> >>>Consider this 4gl program: >>... >>> LET a[c] = b[c] = 0 >>... >>>John Maddox (jmaddox@dbaix.oc.com) * OpenConnect Systems * Tel: 214-490-4090 >> >>This is incorrect LET syntax, whatever the behavior. > >Correct; this is a C-ism. > >>Undesired results when the product is used inconsistently with the >>documentation are not considered bugs... The interesting ones can >>be submitted as feature requests, though. > >Not exactly. Just because a programmer uses improper syntax doesn't mean >s/he deserves whatever bad thing happens. In this case, the compiler >should be smart enough to trap this as a syntax error. Correct, certain types of undesired results are considered bugs, such as core dumps from incorrect syntax, and as in this case, when incorrect syntax is not caught by the pre-processor. >This particular type of usage *is* recorded as a bug (#11371). To clarify, the bug is not that a[c] is not set to 0, but that the syntax error is not trapped. The bug description is: "LET A = B = C DOES NOT PRODUCE SYNTAX ERROR." >>Craig > >Alan Denney # aland@informix.com # {pyramid|uunet}!infmx!aland