Re^3: what would you like to see in perl5.12?

in reply to Re^2: what would you like to see in perl5.12?
in thread what would you like to see in perl5.12?

And does Moose magically turns on strict and warnings in all packages used by your script?

I'd like to see strict and warnings on by default, but it ain't going to happen. It would break too much Perl code, including that on CPAN.

Comment on Re^3: what would you like to see in perl5.12? Select or Download Code

Replies are listed 'Best First'.
Re^4: what would you like to see in perl5.12? by EvanCarroll (Chaplain) on Aug 19, 2007 at 23:59 UTC
No, it doesn't and it just as well shouldn't, but could. I like strict and warnings in use in my code, because it means I'm less likely to create a maintenance nightmare for myself. But as far as other peoples code, they can create as much of a maintenance nightmare for themselves as their heart desires. ;) Just add a `use Moose;` at the top if your script and you too can have strict and warnings on by default for whatever package you're in. The next logical question that I'm at, is if Moose further cuts down dev/maintenance time how too can I avoid this redundant step of `use`ing it. There isn't an easy answer that will allow you to maintain backwards compatibility but shipping Moose as a core module would make widespread development a reality. Evan Carroll www.EvanCarroll.com	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^4: what would you like to see in perl5.12?
by EvanCarroll (Chaplain) on Aug 19, 2007 at 23:59 UTC

No, it doesn't and it just as well shouldn't, but could. I like strict and warnings in use in my code, because it means I'm less likely to create a maintenance nightmare for myself. But as far as other peoples code, they can create as much of a maintenance nightmare for themselves as their heart desires. ;)

Just add a use Moose; at the top if your script and you too can have strict and warnings on by default for whatever package you're in. The next logical question that I'm at, is if Moose further cuts down dev/maintenance time how too can I avoid this redundant step of useing it. There isn't an easy answer that will allow you to maintain backwards compatibility but shipping Moose as a core module would make widespread development a reality.

Evan Carroll
www.EvanCarroll.com

[reply]
[d/l]
[select]

In Section Meditations