We don't bite newbies here... much | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
What you are really saying is: Use of new features considered harmfulYou are of course allowed to have any opinion you want, but I strongly disagree. The new features make some things much easier and that is worth the trouble in my opinion. I think neither the original title nor my rewrite of it really do anything about the real problem you have. I humbly propose the following statement: Use of ANCIENT PERL considered painful Perl 5.005_03 is 5 years old. I'll buy a crate of beer for the first person who can show me some real-world code which absolutely requires our and can't be re-written to use my. With those unstrict rules, it's easy: This cannot be rewritten with my, because then things start to break. It can be rewritten using use vars, but you didn't mention that at all. Juerd # { site => 'juerd.nl', plp_site => 'plp.juerd.nl', do_not_use => 'spamtrap' } In reply to Re: Use of 'our' considered harmful
by Juerd
|
|