Exactly. Especially since the silly comment also missed the point that I noticed as an obvious issue when I read the spec for Modern::Perl and that may have been the point of this thread. Code that uses Modern:Perl will be more likely to break when Modern::Perl or perl is updated since the spec declares that the state exposed by Modern::Perl will change (and in unspecified or unforeseen ways).
Cute name. Cute idea. Not something I'll be using as spec'd.
| [reply] |
Code that uses Modern:Perl will be more likely to break when Modern::Perl or perl is updated....
First, it's not for you. You're a Perl guru. You don't need it. You know how to twist and mold Perl to behave how you like through pragmas and modules.
Second, I'm likely to add a year flag, so that people can (optionally) request a specific-but-recent version of modernity.
Third, anyone who blindly upgrades code without testing it has bigger problems than a silly little module like this.
| [reply] |
Bigger problems, like being a beginner and not knowing any better? ;)
/J
| [reply] |
