Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl-Sensitive Sunglasses
 
PerlMonks  

Re^3: [OT] Why I don't use Mysql for new projects (strictperl)

by chromatic (Archbishop)
on Jul 11, 2009 at 08:25 UTC ( #779160=note: print w/replies, xml ) Need Help??


in reply to Re^2: [OT] Why I don't use Mysql for new projects
in thread [OT] Why I don't use Mysql for new projects

I'd stick with perl for my old scripts that aren't strict safe, and chose the strictperl version for everything that I newly write.

Good news: strictperl exists (though it only enables strict; warnings are more problematic conceptually.)

Bad news: it's a patch against bleadperl and much of the Perl core does not run with strict enabled unilaterally.

Replies are listed 'Best First'.
Re^4: [OT] Why I don't use Mysql for new projects (strictperl)
by Corion (Pope) on Jul 11, 2009 at 08:53 UTC

      The use 5.11; feature is good and welcome, but its goal is very different: to reduce the amount of boilerplate necessary to enable newer features. The goal of strictperl is to experiment with a Perl that forces you to be explicit about where you need to avoid strictures; it's an experiment in maintainability and reliability in Perl 5. (The suggestion "Can't you just use a source filter?" I find silly.)