Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What should "use perl5i" do? #69

Closed
schwern opened this issue Jan 23, 2010 · 2 comments
Closed

What should "use perl5i" do? #69

schwern opened this issue Jan 23, 2010 · 2 comments

Comments

@schwern
Copy link
Contributor

schwern commented Jan 23, 2010

(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.

@clonezone
Copy link

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;".

@schwern
Copy link
Contributor Author

schwern commented Jan 28, 2010

It is done. "use perl5i" is an error. "use perl5i::0" and "use perl5i::latest" are the new way.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants