-
Notifications
You must be signed in to change notification settings - Fork 560
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
Special-case "use v6" #16007
Comments
From juerd@tnx.nlCurrently, "use v6" run by perl 5 results in something like: Perl v6.0.0 required--this is only v5.24.1, stopped at foo.p6 line 3. The message "this is only", especially the word "only", shows that it's Besides that, Perl 6 doesn't use version numbers like "6.0.0"; the I think v6 should be special-cased. My suggestion would be to simply Perl 6 required--this is Perl 5, stopped at foo.p6 line 3. and to support anything after the period, so that even the weird "6.c" Juerd Waalboer <juerd@tnx.nl> |
From @avarOn Thu, Jun 8, 2017 at 9:08 PM, Juerd Waalboer
Related to this: Is there no such thing as an integration plan for p5 There's Inline::Perl[56] modules for perl6 & perl5 respectively which That would allow "use v6" do DWYM instead of erroring out, wasn't that In any case, maybe that's not going to happen, but changing the error |
The RT System itself - Status changed from 'new' to 'open' |
From @xsawyerxOn 06/09/2017 11:13 AM, Ævar Arnfjörð Bjarmason wrote:
I think both of these are too committal. If you say "*yet*," you will |
From @cpansproutOn Thu, 08 Jun 2017 12:08:04 -0700, juerd@tnx.nl wrote:
But leave the full Perl 5 version in. There is no need to special-case that part of the message, and it is still useful information for the user regardless. -- Father Chrysostomos |
From zefram@fysh.orgJuerd Waalboer wrote:
+1.
That sounds like a special case too far: it would require a non-trivial -zefram |
Migrated from rt.perl.org#131538 (status was 'open')
Searchable as RT131538$
The text was updated successfully, but these errors were encountered: