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

Re: Announcing Perl 7

Thread Previous | Thread Next
Paul "LeoNerd" Evans
June 27, 2020 11:18
Re: Announcing Perl 7
Message ID:
On Fri, 26 Jun 2020 14:46:10 +0100
Dave Mitchell <> wrote:

> On Fri, Jun 26, 2020 at 02:49:31PM +0200, demerphq wrote:
> > To achieve this change requiring new code to include "use v7" is a
> > non-starter.  
> This is the bit I fundamentally don't understand. Convince me of this,
> and most of my objections will fizzle away.
> 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.
> 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.

Plus a "use v7" at the top of a file will be a BIG HINT to things like
Github syntax highlighting, vim/emacs/other editors and IDEs ... so
many places, that they should pick syntax highlighting relevant to Perl
7, not Perl 5.

Alright right now I am in quite a mixed place, trying to have vim
support both signatures and pre-signature prototype notations. It would
be alot easier if vim had a standard signal to look for, to tell it
*which* set of two different kinds of syntax rules to apply to *.pm

  use v7;

would be a very easy signal to look for.

I can imagine the github/ highlighters would also appreciate such
a useful signal.

Alternatively, if you are really fundamentally strongly suggesting not
to bother with a "use v7" them please explain to vim, emacs, github,
and all those other places, how they are supposed to syntax highlight a
*.pm file.

Paul "LeoNerd" Evans      |  |

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