"Prof. A Olowofoyeku (The African Chief)" wrote:
On 15 Dec 2003 at 8:39, CBFalconer wrote: [...]
IIRC the original complaint, since snipped, applied to BP and attempted to use a null statement after a conditional. It seems to me that there is absolutely no need for such a statement in BP, since ParamCount begins life there as a global variable, and it would probably not be good form to redefine it.
This focus on ParamCount is a red herring. That was just a trivial test program (as Frank always emphasises) that shows the problem. ParamCount is not the problem here. Rather, it is the warning about a ";" following a "then" that was being highlighted.
My point, which I probably did not make clear, is that the only use for a null statement after a then is to discard something in the conditional part. Having discarded the need for this by using clearer methods, such a null THEN clause is clearly a programmatic error and a warning can only be useful.