Re: Drop here docs altogether? (was Re: RFC 111 (v3) Here Docs Terminators (Was Whitespace and Here Docs))

[Glenn Linderman]

Nathan Wiger wrote:

> Solves problem #1, indented terminator, except that it adds two newlines
> (more later).

I never found anything later about these extra newlines... so if this idea
has merit, it needs to be finished.

> However, it leaves 2 and 3. Let's try adding in a regexp:
>
>    if( $is_fitting && $is_just ) {
>          (my $mesg = qq/
>              The old lie
>            Dulce et decorum est
>                Pro patria mori.
>          /) =~ s/\s{8}(.*?\n)/$1/g;
>          die $mesg;
>    }

I think $mesg wins up with the value of "1" the way you've coded it.  You
cured that issue with the RFC 164 syntax for subst, of course, but it could
be cured without that, but does require a temp var.

> I think we're trying to jam alot of stuff into here docs that maybe
> shouldn't be jammed in

Yes, all we need is to recognize the terminator when embedded in white space
on its line, and the rest can be handled with "here doc postprocessing
functions".  Per my somewhat longer reply to Michael Schwern.

I agree with need for a multiple character termination sequence for easy to
write here docs.

--
Glenn
=====
There  are two kinds of people, those
who finish  what they start,  and  so
on...                 -- Robert Byrne



_____NetZero Free Internet Access and Email______
   http://www.netzero.net/download/index.html