user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
* [PATCH] doc: technical/whyperl: update w/ (good) news from PSC
@ 2021-04-13 19:29 Eric Wong
  2021-04-13 19:44 ` upcoming perl v5.12 requirement Eric Wong
  0 siblings, 1 reply; 4+ messages in thread
From: Eric Wong @ 2021-04-13 19:29 UTC (permalink / raw)
  To: meta

It looks like stability and compatibility will prevail, after all.
---
 Documentation/technical/whyperl.txt | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/Documentation/technical/whyperl.txt b/Documentation/technical/whyperl.txt
index de6f912a..fbe2e1b1 100644
--- a/Documentation/technical/whyperl.txt
+++ b/Documentation/technical/whyperl.txt
@@ -66,9 +66,11 @@ Good Things
   Perl had fewer breaking changes than Python or Ruby; we
   expect that trend to continue given the inertia of Perl 5.
 
-  Note: this document was written before the Perl 7 announcement.
-  We'll continue to monitor and adapt to the situation around
-  what distros are doing in regard to maintaining compatibility.
+  As of April 2021, the Perl Steering Committee has confirmed
+  Perl 7 will require `use v7.0' and existing code should
+  continue working unchanged:
+  https://nntp.perl.org/group/perl.perl5.porters/259789
+  <CAMvkq_SyTKZD=1=mHXwyzVYYDQb8Go0N0TuE5ZATYe_M4BCm-g@mail.gmail.com>
 
 * Built for text processing
 

^ permalink raw reply	[flat|nested] 4+ messages in thread

* upcoming perl v5.12 requirement...
  2021-04-13 19:29 [PATCH] doc: technical/whyperl: update w/ (good) news from PSC Eric Wong
@ 2021-04-13 19:44 ` Eric Wong
  2021-04-13 21:17   ` Konstantin Ryabitsev
  0 siblings, 1 reply; 4+ messages in thread
From: Eric Wong @ 2021-04-13 19:44 UTC (permalink / raw)
  To: meta

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

It also allows "delete local" and some other things, but
I'm not yet sure about the "unicode_strings" feature bit...

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: upcoming perl v5.12 requirement...
  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
  0 siblings, 1 reply; 4+ messages in thread
From: Konstantin Ryabitsev @ 2021-04-13 21:17 UTC (permalink / raw)
  To: Eric Wong; +Cc: meta

On Tue, Apr 13, 2021 at 03:44:35PM -0400, 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).

As long as we can set the low bar at 5.16, I'm good with that. Lore will
eventually roll onto newer platforms than CentOS7, but there's still a lot of
yak left to shave before that happens. :)

-K

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: upcoming perl v5.12 requirement...
  2021-04-13 21:17   ` Konstantin Ryabitsev
@ 2021-04-14  0:25     ` Eric Wong
  0 siblings, 0 replies; 4+ messages in thread
From: Eric Wong @ 2021-04-14  0:25 UTC (permalink / raw)
  To: meta

Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
> On Tue, Apr 13, 2021 at 03:44:35PM -0400, 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).
> 
> As long as we can set the low bar at 5.16, I'm good with that. Lore will
> eventually roll onto newer platforms than CentOS7, but there's still a lot of
> yak left to shave before that happens. :)

No problem.  The Perl requirement will crawl forward as slowly as
enterprise/LTS distros go.  I have no plans to skip 5.14, either
(haven't started looking at perl514*delta, and won't until we're
on 5.12).

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2021-04-14  0:25 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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

user/dev discussion of public-inbox itself

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://public-inbox.org/meta
	git clone --mirror http://czquwvybam4bgbro.onion/meta
	git clone --mirror http://hjrcffqmbrq6wope.onion/meta
	git clone --mirror http://ou63pmih66umazou.onion/meta

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V1 meta meta/ https://public-inbox.org/meta \
		meta@public-inbox.org
	public-inbox-index meta

Example config snippet for mirrors.
Newsgroups are available over NNTP:
	nntp://news.public-inbox.org/inbox.comp.mail.public-inbox.meta
	nntp://7fh6tueqddpjyxjmgtdiueylzoqt6pt7hec3pukyptlmohoowvhde4yd.onion/inbox.comp.mail.public-inbox.meta
	nntp://ie5yzdi7fg72h7s4sdcztq5evakq23rdt33mfyfcddc5u3ndnw24ogqd.onion/inbox.comp.mail.public-inbox.meta
	nntp://4uok3hntl7oi7b4uf4rtfwefqeexfzil2w6kgk2jn5z2f764irre7byd.onion/inbox.comp.mail.public-inbox.meta
	nntp://news.gmane.io/gmane.mail.public-inbox.general
 note: .onion URLs require Tor: https://www.torproject.org/

code repositories for project(s) associated with this inbox:

	https://80x24.org/public-inbox.git

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git