Beefy Boxes and Bandwidth Generously Provided by pair Networks
good chemistry is complicated,
and a little bit messy -LW
 
PerlMonks  

Comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

While I realize that this is a 'quick reference', you can get a lot more -- and also quick info -- by typing 'perldoc perlvar' at the command line. For example, while $^V does indeed hold the perl version, to get the string representation of it, you need to use sprintf('%vd, $^V);. So yes, this is useful, but perlvar really isn't that difficult to pull up and it holds a little more info.


In reply to Re: Perl Special Variables Quick Reference by Anonymous Monk
in thread Perl Special Variables Quick Reference by davido

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.
  • Log In?
    Username:
    Password:

    What's my password?
    Create A New User
    Chatterbox?
    [ambrus]: was this bug: https://rt.cpan. org/Public/Bug/ Display.html?id= 59814
    [Corion]: ambrus: Oh - that one would be much harder to automate... The SYNOPSIS section should mostly be a runnable program IMO, but I write only small snippets in my documentation for single functions/methods, and creating the appropriate environment for ...
    [Corion]: ... those in an automated fashion seems somewhat hard to me. Although it should do wonders for the test coverage ;)
    [haukex]: Corion: I once wrote an automated thingy for that here
    [haukex]: here's the code that uses it
    [Corion]: haukex: Hmm - maybe I can reuse that. I see that it uses Pod::Parser, which I think was one of the more fragile parsers. But if I'm statically (re)generating the tests instead of doing that "live" on the client/tester machines, that's a much smaller...
    [Corion]: ... problem space than trying to cater to all versions of Pod::Parser(s)

    How do I use this? | Other CB clients
    Other Users?
    Others perusing the Monastery: (10)
    As of 2017-02-27 12:20 GMT
    Sections?
    Information?
    Find Nodes?
    Leftovers?
      Voting Booth?
      Before electricity was invented, what was the Electric Eel called?






      Results (385 votes). Check out past polls.