Add glossary search to Pod::Perldoc

[illandan]

This one searches in the existing 'perlglossary.pod' file and spits out text/descriptions against matching =items

Examples:

$ perldoc -u -g BSD
=encoding utf8

=over 8

=item BSD

A X<BSD (Berkeley Standard Distribution)>X<Berkeley Standard Distribution
(BSD)>psychoactive drug, popular in the ’80s, probably developed at UC
Berkeley or thereabouts. Similar in many ways to the prescription-only
medication called “System V”, but infinitely more useful. (Or, at least,
more fun.) The full chemical name is “Berkeley Standard Distribution”.

=back
$ perldoc -u -g signal
=encoding utf8

=over 8

=item signal

A bolt X<signals and signal handling, about>out of the blue; that is, an
event triggered by the B<operating system>, probably when you’re least
expecting it.

=item signal handler

A B<subroutine> that, X<handlers, signal>instead of being content to be
called in the normal fashion, sits around waiting for a bolt out of the
blue before it will deign to B<execute>. Under Perl, bolts out of the blue
are called signals, and you send them with the C<kill> built-in. See the
C<%SIG> hash in Camel chapter 25, “Special Names” and the section “Signals”
in Camel chapter 15, “Interprocess Communication”.

=back

[briandfoy]

I've just taken over the maintenance of Pod::Perldoc, so I'll look into this. I know it's years old, and it might take me a bit to catch up.

[briandfoy]

I see this change and it's something I agree with and support. However, I want to land and test some of the backlog first. Once those things stabilize, I will look at merging this. The only hold-up is me being cautious.

[illandan]

Thanks @briandfoy - I can understand this module has some catching up to do with the backlog both on RT and here. I don't remember much of the things that I noticed were broken when I was writing this, except one.

If my memory serves right, there were some parts of perlglossary.pod that didn't agree with the renderers for spitting out unicode output. There was a PR or two that addressed this: you may want to look at merging those ahead of this one and see if formatting/rendering problems are fixed.

[illandan]

@briandfoy I might have some time in the next few weeks. Is there anything I can do to help move this forward?

[briandfoy]

@illandan What I really need are comprehensive tests on this feature, and I haven't had time to write them.

And, in front of that, I need to figure out all of the current test failures.

[illandan]

@briandfoy If you're referring to this, my cursory reading seems to indicate failures on older Perl versions < 5.18. Did we bump the minimum perl version required here?

Anyway, I'll take a look at adding tests for this feature sometime later this month. 👍🏼

[briandfoy]

The test failures are from the accidental and unauthorized release I made under my old username: 3.29