[PATCH 0/4] a few minor doc updates

[PATCH 0/4] a few minor doc updates

[Eric Wong]

It seems eventually we'll need to have "use v5.10.1" at the top
of every source file...  Maybe more Inline::C is coming, since
it's still got the "feel" of working in a scripting language,
mostly...

But maybe there's no point in worrying about Perl 5 being
dropped when Perl 8 comes along after 7 if the world ends this
year :P

Eric Wong (4):
  git: use v5.10.1, parent.pm and Time::HiRes::stat
  doc: daemon: update documentation around Inline::C
  doc/technical/whyperl: reword bit around installed docs
  doc/technical/whyperl: add a bit about Perl 7 announcement

 Documentation/public-inbox-daemon.pod |  4 ++--
 Documentation/technical/whyperl.txt   | 10 +++++++---
 lib/PublicInbox/Git.pm                |  7 ++++---
 3 files changed, 13 insertions(+), 8 deletions(-)

[PATCH 1/4] git: use v5.10.1, parent.pm and Time::HiRes::stat

[Eric Wong]

parent.pm is leaner than base.pm, and Time::HiRes::stat is
more accurate, so take advantage of these Perl 5.10+-isms
since it's been over a year since we left 5.8 behind.
---
 lib/PublicInbox/Git.pm | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/lib/PublicInbox/Git.pm b/lib/PublicInbox/Git.pm
index 776e4832..265524ff 100644
--- a/lib/PublicInbox/Git.pm
+++ b/lib/PublicInbox/Git.pm
@@ -8,15 +8,16 @@
 # There are also API changes to simplify our usage and data set.
 package PublicInbox::Git;
 use strict;
-use warnings;
+use v5.10.1;
+use parent qw(Exporter);
 use POSIX ();
 use IO::Handle; # ->autoflush
+use Errno qw(EINTR);
 use File::Glob qw(bsd_glob GLOB_NOSORT);
+use Time::HiRes qw(stat);
 use PublicInbox::Spawn qw(popen_rd);
 use PublicInbox::Tmpfile;
-use base qw(Exporter);
 our @EXPORT_OK = qw(git_unquote git_quote);
-use Errno qw(EINTR);
 our $PIPE_BUFSIZ = 65536; # Linux default
 our $in_cleanup;
 

[PATCH 2/4] doc: daemon: update documentation around Inline::C

[Eric Wong]

`~/.cache/public-inbox/inline-c' is supported, nowadays
for convenience, but Inline::C usage will remain opt-in.
---
 Documentation/public-inbox-daemon.pod | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/public-inbox-daemon.pod b/Documentation/public-inbox-daemon.pod
index 6091e8e6..747c1452 100644
--- a/Documentation/public-inbox-daemon.pod
+++ b/Documentation/public-inbox-daemon.pod
@@ -142,8 +142,8 @@ enables the use of L<vfork(2)> which speeds up subprocess
 spawning with the Linux kernel.
 
 public-inbox will never enable L<Inline::C> automatically without
-this environment variable set.  See L<Inline> and L<Inline::C>
-for more details.
+this environment variable set or C<~/.cache/public-inbox/inline-c>
+created by a user. See L<Inline> and L<Inline::C> for more details.
 
 =back
 

[PATCH 3/4] doc/technical/whyperl: reword bit around installed docs

[Eric Wong]

I originally proposed this rewording to address Leah's comment
but forgot to squash it in :x

Link: https://public-inbox.org/meta/20200408221741.GA10142@dcvr/
Cc: Leah Neukirchen <leah@vuxu.org>
---
 Documentation/technical/whyperl.txt | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/Documentation/technical/whyperl.txt b/Documentation/technical/whyperl.txt
index b0a0d16b..01ce71e2 100644
--- a/Documentation/technical/whyperl.txt
+++ b/Documentation/technical/whyperl.txt
@@ -26,9 +26,9 @@ Good Things
   have to waste bandwidth or space with giant toolchains or
   architecture-specific binaries.
 
-  Furthermore, Perl documentation is typically installed as
-  manpages, allowing users to quickly access and learn it
-  offline.
+  Furthermore, Perl documentation is typically installed
+  locally as manpages, allowing users to quickly refer
+  to documentation as needed.
 
 * Scripted, always editable by the end user
 

[PATCH 4/4] doc/technical/whyperl: note Perl 7 announcement

[Eric Wong]

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