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

RE: Announcing Perl 7

Thread Previous | Thread Next
From:
Konovalov, Vadim
Date:
June 26, 2020 21:01
Subject:
RE: Announcing Perl 7
Message ID:
MN2PR19MB403228E823B6E9AE93E4C07C8A930@MN2PR19MB4032.namprd19.prod.outlook.com
-----Original Message-----
From: Dave Mitchell <davem@iabyn.com> 

> In my world, the big first public release of 7.0.0 will come along with lots of
> explanations and docs all saying that "if you are writing modern perl, then the
> first thing you need to do is add 'use v7;' to the top of
> your script" - in the
> same way that 'use strict; use warnings' has been
> the mantra for the last 20
> years.

I think this angle of view of word "modern" isn't wise.

IMO "modern" means supporting modern programming techniques:
 - webasm (there was a thread about webperl ,but I don't see it in recent perl)
 - multithreading (deprecated several years ago?)
 - llvm build (I want llvm@win32)
 - etc

The point "modern" === "use strict; use warnigns;" -- I don't buy it. 
Yet warnings.pm is too bloated, to my taste (so I don't use it, but this 
is another story)

I admit - the "use strict" feature is very good selling point of Perl.
But if the language does not support anything except "use strict" - then 
it is hardly useful.


> People learning perl for the first time will know nothing other than to
> add 'use v7'. People working for big companies with coding standards
> will be
> told to put 'use v7' at the top of each script.

This seems unwise to me.

Are there any modern languages that require some version on the top 
of the program?
Not in C++, Rust, Javascript - AFAIK

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