develooper Front page | perl.perl5.porters | Postings from July 2020

Re: Announcing Perl 7

Thread Previous | Thread Next
From:
Christian Walde
Date:
July 3, 2020 17:36
Subject:
Re: Announcing Perl 7
Message ID:
op.0m6wh4weydyjqt@xenwide.vpn.udag.de
On Fri, 03 Jul 2020 19:33:20 +0200, demerphq <demerphq@gmail.com> wrote:

> On Fri, 3 Jul 2020 at 19:19, Paul "LeoNerd" Evans
> <leonerd@leonerd.org.uk> wrote:
>>
>> On Thu, 2 Jul 2020 11:56:19 -0400
>> Dan Book <grinnz@gmail.com> wrote:
>>
>> > FYI, I have collected my core thoughts on the discussion here:
>> > http://blogs.perl.org/users/grinnz/2020/07/perl-7-a-risk-benefit-analysis.html
>>
>> (to copy my comment on the post, for posterity of the mailing list)
>>
>> A huge +1 to all of this. Thank you for articulating it so coherently. I
>> am in entire agreement with this whole idea.
>
> So if I understand you both correctly, we have to continue to support
> all perl 5 code forever?
>
> Because that is what I understand you to be saying.
>
> To me this question comes down to a simple technical question: what
> language variant does the parser start out expecting before it sees
> the "use v7" line?
>
> If we say "perl 5" then we have to support all of perl 5 forever don't we?
>
> Doesn't that kind of er, stand in the way of not supporting perl 5 forever?
>
> Doesn't it make a lot more sense to say "prior to seeing a C<use
> v$DIGIT;> statement the parser will be expecting the *latest* variant
> of the language"? Isn't the certainty of that the only sane choice if
> we are ever to deprecate older variant code?
>
> cheers,
> Yves
>

As mentioned in the reply i sent just previously: You can have versions mandatory and still have the interpreter "forget" Perl 5.

-- 
With regards,
Christian Walde

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About