Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

jmcnamara (659)

jmcnamara
  (email not shown publicly)
http://search.cpan.org/author/jmcnamara/


'ere I am, J.M.! The ghost in the machine:

perl -MCPAN -e 'install jmcnamara & _ x ord $ ;' | tail -1

Journal of jmcnamara (659)

Friday August 08, 2003
05:37 PM

There-doc

[ #14007 ]
there-doc (n): an indented here-doc.

    if ($greeting) {

        print << 'EOT';
        hello, world
        EOT

    }

There's no here here.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • RFC::Prototype::111 (Score:5, Interesting)

    by schwern (1528) on 2003.08.08 19:59 (#22922) Homepage Journal
    See also RFC::Prototype::111 [pobox.com] from back in the initial Perl 6 days. Specificly RFC::Prototype::111. It would be nice if feature #2 was implemented, ie. here-docs not being so sensitive about trailing whitespace in the terminator. PS Would using "code" instead of "executable" for your filter solve the problem of filtering inside strings?
    • Thanks for the suggestions, I'll have a read of RFC111 and add that feature in the next version.

      I did try using "code" in the filter when I was first writing the module, however because "code" removes here documents (see &Text::Balanced::extract_quotelike) it doesn't see the terminator strings until the indenting has been removed. Bit of a chicken and egg situation! What I'll try next is to run Text::Balanced over the current line (when a << has been seen) to identify if the << is part of a