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

Re: Announcing Perl 7

Thread Previous | Thread Next
James E Keenan
June 27, 2020 18:09
Re: Announcing Perl 7
Message ID:
On 6/27/20 1:49 PM, Charles McGarvey wrote:
> I'm still forming my opinions of the perl7 plan and still have questions that
> need answers, but I will say for now that if I take a step back and consider
> what I would want to see in a language that I'm pretending to have no
> emotional attachment to, I think I'd have to say "use v" makes more sense than
> "use compat::perlV". But I'll keep an open mind.

I appreciate what you say there.  In discussing this proposal, each of 
us has to be mindful of our strong emotional attachment to Perl.

> Maybe it's because I already use "use v" and so am acclimated to this idea,
> but if Perl 7 was released under the current plan and I wanted to write
> software targeting it, I would be tempted to include as boilerplate "use
> compat::perl7" even if Perl 8 wasn't available yet, because I know someday
> Perl 8 (or later) will be released with altered syntax and I don't want to
> have to come back to code that is already working just to add a
> "compat::perl7" just so that it continues to work in newer perls (at least
> until any deprecated syntax I'm using gets removed, which is fine).

My everyday boilerplate starts out with 'use 5.14.0; use warnings;' -- 
because that's what gets me:

* strict
* say
* // and //=
* s//r

... which is just about all the post-5.8 syntax I use.  I doubt I've 
ever written a line of Perl code that needed 5.16 or later.  But, then 
again, I'm not $employed now so I would mainly be classified as 
"hobbyist."  Where I last worked (four years ago), developers on a 
different, new project we're able to target 5.24 -- and that looked 
really interesting.


Thread Previous | Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About