On May 2, 2008, at 6:38 PM, Micheal J wrote:
> Not really an issue since this should be properly written as:
>
>  (
>     'else' s=stat     ...{$s.st}
>  )?
>
> Then 's' is never used unless an else clause is present in the input.

can't always... in the -> template or ASt rewrite might need it.

>> For 3.1, we have guarded all of those property references
>> with s!=null?
>> s.st:null. That is good.
>
> Those checks are avoidable. The CPU cycles are better spent  
> elsewhere...

Quite painful was the consensus earlier.

>> I agree with Jim too.
>
>> Is it okay for me to remove the stack guards for dynamic
>> scoping stuff?  quick change to these two templates.
>
> Removing all the [avoidable] guards is the smart thing to do IMHO.

done.
Ter
>
_______________________________________________
antlr-dev mailing list
[email protected]
http://www.antlr.org:8080/mailman/listinfo/antlr-dev

Reply via email to