From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <e@80x24.org>
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net
X-Spam-Level: 
X-Spam-ASN:  
X-Spam-Status: No, score=-4.0 required=3.0 tests=ALL_TRUSTED,AWL,BAYES_00
	shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2
Received: from localhost (dcvr.yhbt.net [127.0.0.1])
	by dcvr.yhbt.net (Postfix) with ESMTP id B5CCC1F953
	for <meta@public-inbox.org>; Mon,  8 Nov 2021 18:38:59 +0000 (UTC)
Date: Mon, 8 Nov 2021 18:38:59 +0000
From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: Re: upcoming perl v5.12 requirement...
Message-ID: <20211108183859.GA25072@dcvr>
References: <20210413192920.42920-1-e@80x24.org>
 <20210413194435.GA3371@dcvr>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <20210413194435.GA3371@dcvr>
List-Id: <meta.public-inbox.org>

Eric Wong <e@80x24.org> wrote:
> On a side note, I'm strongly considering moving to Perl 5.12
> after public-inbox 1.7 is released.  perl 5.12.4 will be a
> decade old in a few months (however 5.12.5 was Nov 2012).
> 
> It seems the various 5.12.x releases had fewer breaking bugfixes
> than 5.10.0 => 5.10.1, so "use v5.12" should be fine.
> 
> The main reason I want 5.12 is it enables strict implicitly,
> reducing syscalls and startup time:
> 
>   strace -c perl -Mstrict -e exit # 208 syscalls
>   strace -c perl -Mv5.12 -e exit  # 186 syscalls

Unfortunately, that makes no difference for anything which uses
modules in the Perl stdlib or any 3rd-party modules.  Even if we
relied on v5.12 for strict, all external dependencies we load
"use strict" and they remain Perl 5.8 (if not 5.6) compliant.

> It also allows "delete local" and some other things, but

That's nice, as is //a for ASCII-only matches.

> I'm not yet sure about the "unicode_strings" feature bit...

This requires much care on our part, unfortunately.