in reply to Re^25: Why is the execution order of subexpressions undefined?
in thread Why is the execution order of subexpressions undefined?

tilly,
Have you changed your mind or lost it? At least twice in the past, you have said there are 2 neccessary uses of traditional goto in Perl. Even if you didn't mean necessary, you still said two.

Cheers - L~R

For anyone who doesn't have a sense of humor, suggesting that tilly might have lost his mind is a joke
  • Comment on Re^26: Why is the execution order of subexpressions undefined?

Replies are listed 'Best First'.
Re^27: Why is the execution order of subexpressions undefined?
by tilly (Archbishop) on Apr 23, 2005 at 01:20 UTC
    My mind has not changed, and I have not lost it. I have seen 2 good reasons to use the traditional goto in Perl, and I describe both above.

    One was in Switch. The other is in the output of an automatic translator. (I originally said the wrong one, it is s2p that spit out lots of gotos, because sed code has lots of gotos in it.) I believe that the other was the original reason to have goto in Perl - Larry Wall wanted to convince people that they could learn Perl and do what they did with awk and sed, plus more, with just one tool. The automatic translation utilities made this feasible. But they would have been hard to write if you weren't allowed translate goto to goto.