Point taken. :)

But in the case of Carp, my Carp.pm uses goto in the same magical way that it's used in AUTOLOAD:

    goto &longmess;
[download]

The purpose being that this magical goto erases the calling function from the call stack, which is exactly why it's used here: since longmess dumps out a stack trace, we don't want shortmess showing up in the call stack.

So you should let Carp.pm slide, too. :)

BTW, I like the perlfunc entry for goto:

goto - create spaghetti code
[download]