On Mon, 28 Aug 2000 10:38:42 -0400 (EDT), Eric Roode wrote:
>People may throw rocks at me for this, but I'd like to suggest that
>not only is a comment allowed on the terminator line, but a semicolon
>also be allowed. Vis:
>
> print <<EOL;
> EOL; # This should work, too
Let me throw the first rock. I think this is confusing for the reader of
your code. This looks like a statement, not an end-of-doc marker, so
they'll search for the definition of the sub EOL.
Next you'll propose that
print <<EOL;
blah
EOL; print "OK!\n";
should work too, and print "OK!\n" as well.
OTOH, what about this...
print <<EOL
blah
EOL;
which makes this a full blown statement (note the missing semicolon in
the first line)...
Nah!
--
Bart.
- RFC 111 (v2) Here Docs Terminators (Was Whitespace and... Perl6 RFC Librarian
- Re: RFC 111 (v2) Here Docs Terminators (Was White... Bart Lateur
- Re: RFC 111 (v2) Here Docs Terminators (Was W... Ariel Scolnicov
- Re: RFC 111 (v2) Here Docs Terminators (Was White... Philip Newton
- Re: RFC 111 (v2) Here Docs Terminators (Was White... Eric Roode
- Re: RFC 111 (v2) Here Docs Terminators (Was W... Bart Lateur
- Re: RFC 111 (v2) Here Docs Terminators (W... Nathan Wiger
- Re: RFC 111 (v2) Here Docs Terminator... Bart Lateur
- Re: RFC 111 (v2) Here Docs Terminator... Tom Christiansen
- Re: RFC 111 (v2) Here Docs Terminators (W... Richard Proctor
- Re: RFC 111 (v2) Here Docs Terminator... Tom Christiansen
- Re: RFC 111 (v2) Here Docs Terminators (Was W... Richard Proctor
- Re: RFC 111 (v2) Here Docs Terminators (W... David L. Nicol
