From: Eric Wong <e@yhbt.net>
To: meta@public-inbox.org
Subject: [PATCH 4/4] doc/technical/whyperl: note Perl 7 announcement
Date: Sun, 5 Jul 2020 22:44:52 +0000 [thread overview]
Message-ID: <20200705224452.6159-5-e@yhbt.net> (raw)
In-Reply-To: <20200705224452.6159-1-e@yhbt.net>
Right now[1] the Perl upstream plan is to maintain 5 compatibility
in Perl 7 for at least 5 years[1], and perhaps drop it when Perl 8
comes along. That said, distros may pick it and maintain 5 on their
own given the vast amounts of perfectly good legacy code out there.
[1] http://nntp.perl.org/group/perl.perl5.porters/257817
[2] http://nntp.perl.org/group/perl.perl5.porters/257565
---
Documentation/technical/whyperl.txt | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/Documentation/technical/whyperl.txt b/Documentation/technical/whyperl.txt
index 01ce71e2..de6f912a 100644
--- a/Documentation/technical/whyperl.txt
+++ b/Documentation/technical/whyperl.txt
@@ -66,6 +66,10 @@ 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.
+
* Built for text processing
Our focus is plain-text mail, and Perl has many built-ins
prev parent reply other threads:[~2020-07-05 22:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-05 22:44 [PATCH 0/4] a few minor doc updates Eric Wong
2020-07-05 22:44 ` [PATCH 1/4] git: use v5.10.1, parent.pm and Time::HiRes::stat Eric Wong
2020-07-05 22:44 ` [PATCH 2/4] doc: daemon: update documentation around Inline::C Eric Wong
2020-07-05 22:44 ` [PATCH 3/4] doc/technical/whyperl: reword bit around installed docs Eric Wong
2020-07-05 22:44 ` Eric Wong [this message]
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200705224452.6159-5-e@yhbt.net \
--to=e@yhbt.net \
--cc=meta@public-inbox.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://80x24.org/public-inbox.git
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).