user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <>
Subject: Re: upcoming perl v5.12 requirement...
Date: Mon, 8 Nov 2021 18:38:59 +0000	[thread overview]
Message-ID: <20211108183859.GA25072@dcvr> (raw)
In-Reply-To: <20210413194435.GA3371@dcvr>

Eric Wong <> 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.

  parent reply	other threads:[~2021-11-08 18:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-13 19:29 [PATCH] doc: technical/whyperl: update w/ (good) news from PSC Eric Wong
2021-04-13 19:44 ` upcoming perl v5.12 requirement Eric Wong
2021-04-13 21:17   ` Konstantin Ryabitsev
2021-04-14  0:25     ` Eric Wong
2021-11-08 18:38   ` Eric Wong [this message]
2022-02-13 10:18     ` Eric Wong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20211108183859.GA25072@dcvr \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).