Re: Is this a bug in 4GL 4.10?

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. This particular type of usage *is* recorded as a bug (#11371). (What's actually happening, I think, is that it gets processed as: LET a[c] = (b[c] = 0) the right expression is undefined (b[*] wasn't initialized), so a[*] will also be garbage.) >Craig -- Alan Denney # aland@informix.com # {pyramid|uunet}!infmx!aland Confidentially, she never called me 'Baby Doll' Confidentially, I never had much pride So now I rock a barstool and I drink for two Just pondering this time bomb in my mind -- "Lucky Ball and Chain", TMBG