in reply to Go to perl::critic

No such policy. Well, just an orthogonal one that marks code as reachable if it has a label.

My counter-question to you is, what's so bad about goto? Food scientists trying to come up with gluten-free spaghetti have no idea computer science had it covered decades ago. Plus it's great for extra artistic renditions of Queen songs that remind me of how much my programming style has changed since Freddie was filling stadiums:

pts/2 ryan@pi:~/src/shorts $> cat #!/usr/bin/env perl use 5.010; use strict; say 'Thunderbolt and lightning, very, very frightening me'; # say 'Galileo' for 1..5 has nothing on this: my $galileos = 5; galileo: say "Galileo"; goto galileo if --$galileos; figaro: say 'Figaro magnifico'; pts/2 ryan@pi:~/src/shorts $> perlcritic source OK

Replies are listed 'Best First'.
Re^2: Go to perl::critic
by Tux (Canon) on Oct 06, 2019 at 10:35 UTC

    Other than that I also get no warning, you should pass -1 to perlcritic to get all levels of warnings. The default is level 5, which does suppress most warnings.

    Enjoy, Have FUN! H.Merijn

      You're right of course. However, after making sure goto wasn't flagged at any level, I took some artistic license to maximize comedic value and minimize snippet length. ;-)

Re^2: Go to perl::critic
by rir (Vicar) on Oct 06, 2019 at 13:42 UTC
    Okay, I'll play the straight man.

    What is wrong with goto is that it can be obfuscating and it can be slow--slow motion slow.