Re^5: Coding styles: OOP vs. Subs

That still seems like bad form to me. Imagine someone comes along and tries to extend it...

use warnings; print ("$_")."blah" for qw /foo, #bar, BAZ/
[download]

Just because you can do something doesn't mean you should. (Not that I'm implying that you should never turn off warnings. The OP's code isn't one of those times though).

Comment on Re^5: Coding styles: OOP vs. Subs Download Code

Replies are listed 'Best First'.
Re^6: Coding styles: OOP vs. Subs by Perl Mouse (Chaplain) on Nov 17, 2005 at 17:29 UTC
Huh? What's your point? Valid code throwing warnings prevents someone from introducing bugs? `Perl --((8:>*`	[reply]
Re^7: Coding styles: OOP vs. Subs by Anonymous Monk on Nov 17, 2005 at 17:52 UTC
The point is, seeing code like that lets a maintenance programmer know that the original coder isn't that familiar with Perl, and to tread with caution, because there are undoubtedly obscure bugs lurking around.	[reply]
Re^8: Coding styles: OOP vs. Subs by Perl Mouse (Chaplain) on Nov 18, 2005 at 09:32 UTC
If a maintenance programmer thinks I'm not familiar with Perl after seeing my code, there's no hope for the programmer. Besides, I'm my own maintenance programmer. `Perl --((8:>*`	[reply]