You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
perl5i wants the ability to make incompatible changes, to fix the mistakes of the past, to avoid painting itself into the same corner Perl 5 is. To that end it needs the ability to declare breaks in the API to the user in a way that won't suddenly break shit. Issue #60 discusses ways to do this.
This leaves the sticky issue of what happens when you write "use perl5i".
On the one hand, "use perl5i" is not safe. It will eventually change its API and break your code. In that light, "use perl5i" should die with instructions on how to use it safely.
OTOH It can be a bit inconvenient to always be declaring what version of perl5i you're currently using. For example, in one liners (though they can use the even more convenient perl5i command line wrapper). Then again, its even more inconvenient when your code suddenly breaks because you didn't know about perl5i's versioning policy.
The text was updated successfully, but these errors were encountered:
I'm for "use perl5i;" being an error. Is it really that difficult to put a "blah => bleh" afterwards? Think of it as equivalent to the implicit use of feature.pm implied by "use version;".
(See http://github.com/schwern/perl5i/issues#issue/60 for full context)
perl5i wants the ability to make incompatible changes, to fix the mistakes of the past, to avoid painting itself into the same corner Perl 5 is. To that end it needs the ability to declare breaks in the API to the user in a way that won't suddenly break shit. Issue #60 discusses ways to do this.
This leaves the sticky issue of what happens when you write "use perl5i".
On the one hand, "use perl5i" is not safe. It will eventually change its API and break your code. In that light, "use perl5i" should die with instructions on how to use it safely.
OTOH It can be a bit inconvenient to always be declaring what version of perl5i you're currently using. For example, in one liners (though they can use the even more convenient perl5i command line wrapper). Then again, its even more inconvenient when your code suddenly breaks because you didn't know about perl5i's versioning policy.
The text was updated successfully, but these errors were encountered: