Beefy Boxes and Bandwidth Generously Provided by pair Networks
Keep It Simple, Stupid
 
PerlMonks  

Re^2: Announcing Perl 7

by hippo (Bishop)
on Jun 25, 2020 at 11:24 UTC ( [id://11118513]=note: print w/replies, xml ) Need Help??


in reply to Re: Announcing Perl 7
in thread Announcing Perl 7

I am somewhat skeptical too. 10 or 15 years ago this would have been great news and would have neatly side-stepped most of the negative attitudes to Perl arising from the schism. However, now that so much water has flown under the bridge and the naming situation was finally resolved last year the potential marketing gain from this is relatively minor.

So for me it all rests on the backwards compatibility. Haven't we all seen how just a few minor incompatible tweaks in recent releases have caused significant numbers of problems? I'm think here mostly of the removal of '.' from @INC and the inability to write for my $foo qw/bar baz/ {...} which broke lots of existing and important modules, many of which remain unpatched.

What I would like to see is a minimally-transparent way to have perl7 behave exactly like perl5 with no caveats. The only way I can see to do this is with an environment variable. It could be set once per server (and overridden per user/app/whatever) and then the job is done. If that can happen (and be thoroughly tested) then I'll be prepared to throw my inconsiderable weight behind it.

The announcement by contrast only mentions a pragma (compat::perl5) which might be usable via $PERL5OPT (or $PERL7OPT more likely). So if we can set PERL7OPT=-mcompat::perl5 then that should be manageable. It's still going to require extensive testing, of course.

In the meantime, I will continue to forge ahead with perl5.

Replies are listed 'Best First'.
Re^3: Announcing Perl 7
by choroba (Cardinal) on Jun 25, 2020 at 14:34 UTC
    > it all rests on the backwards compatibility.

    Watch the announcement. Sawyer talks about people who need that and how Perl treated them in the past, and why it's time to change it.

    map{substr$_->[0],$_->[1]||0,1}[\*||{},3],[[]],[ref qr-1,-,-1],[{}],[sub{}^*ARGV,3]
      Yes, he does talk about it, but I can't say I found it terribly convincing. Particularly given that he characterized "people who don't use (or don't want to use) Perl any more" as the only ones who care about stability or backwards compatibility, and presumed that anyone doing current development wants whiz-bang new features to be added and on by default ASAP, even if it means they have to go back and fix their older code to account for it.

      Can't speak for anyone else, but I currently work with Perl code both as a developer and a sysadmin, I have no intention of reducing or stopping my usage of Perl, and yet I prefer to build on a solid foundation rather than shifting sands.

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://11118513]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others rifling through the Monastery: (6)
As of 2024-03-28 08:12 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found