comment on

I stumbled over Pod::Functions which provides a list of all Perl builtins listed in perlfunc plus short-description.

use strict;
use warnings;
use Data::Dump qw/pp dd/;
use Pod::Functions;

pp '\%Flavor: ', \%Flavor;
pp '\%Type_Description: ', \%Type_Description;
pp '\@Type_Order: ', \@Type_Order;
pp '\%Kinds: ', \%Kinds;
pp '\%Type: ', \%Type;
[download]

(
  "\\%Flavor: ",
  {
    "-X"               => "a file test (-r, -x, etc)",
    "__FILE__"         => "the name of the current source file",
    "__LINE__"         => "the current source line number",
    "__PACKAGE__"      => "the current package",
    "__SUB__"          => "the current subroutine, or C<undef> if not 
+in a subroutine",
    "abs"              => "absolute value function",
    "accept"           => "accept an incoming socket connect",
    "alarm"            => "schedule a SIGALRM",
    "atan2"            => "arctangent of Y/X in the range -PI to PI",
 ...
[download]

But it doesn't have an option to return the usage examples, like

    split /PATTERN/,EXPR,LIMIT
    split /PATTERN/,EXPR
    split /PATTERN/
[download]

any standard recommendation how to get this, without hacking it with Pod::Simple et al?

Cheers Rolf
_{(addicted to the Perl Programming Language and ☆☆☆☆ :)

Wikisyntax for the Monastery}

In reply to POD: getting usage snippets from perldoc by LanX

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


"be consistent"
	PerlMonks