On 2011年6月14日, Roberto Ierusalimschy wrote:
Maybe it would be safer to be a compilation error, but this is tricky. Consider the next, similar code: do goto label do @label: -- 1 end @label: -- 2 end @label: -- 0 Now, when the compiler sees label 0, label 2 and label 1 are out of scope, so it makes no sense to raise an error.It would hurt the compiler to stop on label 2 (raising an error) to avoid confusion?I am talking about the conflict between label 2 and label 0; assume label 1 is not present. How the compiler can stop on label 2?
Sure! And I am talking about the confusion in my mind :-) I understand your point and I think it wouldn't hurt to avoid this situation at all with a compilation error. Regards, Tomás