Once you type 'perl RET', an executable named 'perl' will be started. That program (presumably) will go on to read STDIN and execute it as perl script.

It'd be rather strange for scripts to be self-editing. E.g. your DATA section might contain escape sequences and so on. In theory, one could have perl act differently (launch an IDE) when run on a terminal with no arguments. Via sitecustomize perhaps or by creating a 'perl' wrapper script. You try it, see how it works.

Or you could do what everyone else does: use perl -e '...' multiliners. Or perhaps echo '...' | perl. In other words, edit/enter the script as part of the command line.

In reply to Re: Navigating history of STDIN-multiliners after 'perl RET' by Anonymous Monk
in thread Navigating history of STDIN-multiliners after 'perl RET' by LanX

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, details, 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, summary, 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.