From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: Re: [RFC] start depending on Perl 5.10.1+
Date: Mon, 29 Apr 2019 01:54:09 +0000 [thread overview]
Message-ID: <20190429015409.vxgjuinoiltbgbdd@dcvr> (raw)
In-Reply-To: <20190417220538.25112-1-e@80x24.org>
The one minor, (and likely irrelevant) downside to this change
would be any of code which relies on the 'fields' pragma for
pseudo-hash performance benefits is out-of-luck since
pseudo-hashes were removed in Perl 5.9.
Our only use of the 'fields' pragma is from Danga::Socket
(and descendent) classes. Fwiw, I have never used Perl 5.8 on
public-inbox myself, either.
next prev parent reply other threads:[~2019-04-29 1:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-17 22:05 [RFC] start depending on Perl 5.10.1+ Eric Wong
2019-04-29 1:54 ` Eric Wong [this message]
2019-06-02 20:13 ` 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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://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=20190429015409.vxgjuinoiltbgbdd@dcvr \
--to=e@80x24.org \
--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.
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).