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

It seems that a similar idea has been applied to the Perl core for 5.11, and it'll be enabled through use 5.11;. It applies strict and warnings in a local scope instead of globally, so things that don't work with it don't break. As Rafael Garcia-Suarez points out, globally adding strict+warnings doesn't need a patch to Perl but only a source filter.

Comment on Re^4: [OT] Why I don't use Mysql for new projects (strictperl) Download Code

Replies are listed 'Best First'.
Re^5: [OT] Why I don't use Mysql for new projects (strictperl) by chromatic (Archbishop) on Jul 11, 2009 at 16:34 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.)	[reply] [d/l]

Replies are listed 'Best First'.

Re^5: [OT] Why I don't use Mysql for new projects (strictperl)
by chromatic (Archbishop) on Jul 11, 2009 at 16:34 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.)

[reply]
[d/l]