Re^2: Strictly nested sub warnings

[raybies]

It's probably a stupid question, but why not use prototypes?

I like that I get some argument checking (not a whole lot, but that's actually better most of the time) by declaring named subs (i.e.  sub mySubroutine ($$) has two expected scalar args) with args, but I also like to stuff my subs at the bottom of my file, and so perl issues a warning if I don't put the prototype at the beginning of the code.

Are you suggesting that to become more Perly, one must abandon naming arguments altogether in subs?

Thanks again, all, for the suggestions. --Ray

[eyepopslikeamosquito]

For why not, see Far More than Everything You've Ever Wanted to Know about Prototypes in Perl -- by Tom Christiansen and Perl Best Practices Chapter 9 (Subroutines), "Don't use subroutine prototypes".

[raybies]

Thanks! I was just reading that exact node in the Meditations section... --Ray