Re: RFC 111 (v1) Whitespace and Here Docs

Reply on laptop in wilderness (no network) holydays me void this message by other messages sent in my absence. Ignore if so. On Thu, 17 Aug 2000 08:28:50 -0400 (EDT), Philip Newton <[EMAIL PROTECTED]> wrote: > On Tue, 15 Aug 2000, Michael Fowler wrote: > > > So what's insufficient about: > > >

Re: RFC 111 (v1) Whitespace and Here Docs

On Fri 25 Aug, Nathan Wiger wrote: > > I was sorta going under the assumption that <<< would cause leading and > > trailing whitespace to be ignored (not stripped) when looking for the > > end-of-here-doc indicator. Because whitespace is ignored, I was then > > proposing some new syntax for strip

Re: RFC 111 (v1) Whitespace and Here Docs

On Thu, 24 Aug 2000 21:06:30 -0700, Nathan Wiger wrote: > 1. Ignore leading/trailing whitespace in here string terminators. > All of these should work: > >EOL > EOL >EOL # this is the end of the here doc > > I don't think a special syntax is needed just for this. Make > thi

Re: RFC 111 (v1) Whitespace and Here Docs

> I was sorta going under the assumption that <<< would cause leading and > trailing whitespace to be ignored (not stripped) when looking for the > end-of-here-doc indicator. Because whitespace is ignored, I was then > proposing some new syntax for stripping whatever one likes from the contents >

Re: RFC 111 (v1) Whitespace and Here Docs

>Unfortunately the quoting on the terminator following << decides the type >of interpolation; we're missing a way of indicating how to recognize the >terminator other than an exact match. If we say that we want varia

Re: RFC 111 (v1) Whitespace and Here Docs

On Thu, Aug 24, 2000 at 05:24:14PM -0700, Peter Scott wrote: > At 05:41 PM 8/24/00 -0600, Tom Christiansen wrote: > >But you don't need that when you can and possibly should just write this: > > > > print <<"EOF" =~ /^\s*\| ?(.*\n)/g; > > Others may be focussing on th

Re: RFC 111 (v1) Whitespace and Here Docs

On Thu, Aug 24, 2000 at 05:41:00PM -0600, Tom Christiansen wrote: > But you don't need that when you can and possibly should just write this: > > print <<"EOF" =~ /^\s*\| ?(.*\n)/g; > | Attention criminal slacker, we have yet > | to receive payment for our legal services.

Re: RFC 111 (v1) Whitespace and Here Docs

At 05:41 PM 8/24/00 -0600, Tom Christiansen wrote: >But you don't need that when you can and possibly should just write this: > > print <<"EOF" =~ /^\s*\| ?(.*\n)/g; > | Attention criminal slacker, we have yet > | to receive payment for our legal s

Re: RFC 111 (v1) Whitespace and Here Docs

>Basically, it's shorthand for the current syntax: >$message = <<"EOF" =~ s/^\s*\| ?//g; >| Attention criminal slacker, we have yet >| to receive payment for our legal services. >| >| Love and kisses >| >EOF >print $message; >But any i

Re: RFC 111 (v1) Whitespace and Here Docs

On Thu, Aug 24, 2000 at 05:26:36PM -0600, Tom Christiansen wrote: > >I thought this problem would've been neatly solved by my proposed: > > >print <<<"FOO" =~ s/^ {8}//; > >Attention criminal slacker, we have yet > >to receive payment for our legal services. > > >

Re: RFC 111 (v1) Whitespace and Here Docs

>I thought this problem would've been neatly solved by my proposed: >print <<<"FOO" =~ s/^ {8}//; >Attention criminal slacker, we have yet >to receive payment for our legal services. >Love and kisses >FOO The result of substituting the leading 8 bla

Re: RFC 111 (v1) Whitespace and Here Docs

>Today around 4:30pm, Tom Christiansen hammered out this masterpiece: >: print print <<" FOO" =~ /^\s+(.*\n)/gm; >Unless, of course, you want `xx oo' to be indented still, and the blank >remain. That r

Re: RFC 111 (v1) Whitespace and Here Docs

On Thu, Aug 24, 2000 at 06:14:10PM -0400, Michael G Schwern wrote: > Paragraphs. > > sub legal { > print << Attention criminal slacker, we have yet > to receive payment for our legal services. > > Love and kisses > FOO > } > > Obvi

Re: RFC 111 (v1) Whitespace and Here Docs

Today around 4:30pm, Tom Christiansen hammered out this masterpiece: : print <'[EMAIL PROTECTED]',site=> 'http://home.kiski.net/~crt'};print "\n",'.'x(length($sig->{site})+6),"\n"; print map{$_.': '.$sig->{$_}."\n"}sort{$sig->{$a}cmp$sig->{$b}}keys%{$sig}; my $VERSION = '0.01'; #'patche

Re: RFC 111 (v1) Whitespace and Here Docs

At 04:30 PM 8/24/00 -0600, Tom Christiansen wrote: > >I'm coming into this a bit late, so forgive me if this is impossible or > >already dismissed, but what about > > > print < > Attention, dropsied weasel, we are > > launching our team of legal beagles > >

Re: RFC 111 (v1) Whitespace and Here Docs

>I'm coming into this a bit late, so forgive me if this is impossible or >already dismissed, but what about > print < Attention, dropsied weasel, we are > launching our team of legal beagles > straight for your scrofulous crotch. >

Re: RFC 111 (v1) Whitespace and Here Docs

At 06:14 PM 8/24/00 -0400, Michael G Schwern wrote: >Okay, devil's advocate. > >Paragraphs. > > sub legal { > print << Attention criminal slacker, we have yet > to receive payment for our legal services. > > Love and kisses > FOO > }

Re: RFC 111 (v1) Whitespace and Here Docs

Okay, devil's advocate. Paragraphs. sub legal { print <

Re: RFC 111 (v1) Whitespace and Here Docs

On Tue, 15 Aug 2000, Michael Fowler wrote: > So what's insufficient about: > > print <<"EOF"; > Stuff > More stuff > Even more stuff > EOF Others have already mentioned the "have to count the number of spaces" argument. Another one that comes to mind is: assu

Re: RFC 111 (v1) Whitespace and Here Docs

On Wed, 16 Aug 2000, Perl6 RFC Librarian wrote: > This will ignore all leading white space on each line until the end terminator > is found. It effectively does s/^\s*// before processing each following line. I don't agree with this, but > It also ignores whitespace (but not the line termi

Re: RFC 111 (v1) Whitespace and Here Docs

On Wed, Aug 16, 2000 at 08:22:16PM -0400, Chaim Frenkel wrote: > > "MF" == Michael Fowler <[EMAIL PROTECTED]> writes: > > MF> So what's insufficient about: > > MF> print <<"EOF"; > MF> Stuff > MF> More stuff > MF> Even more stuff > MF> EOF > > > Counting

Re: RFC 111 (v1) Whitespace and Here Docs

> "MF" == Michael Fowler <[EMAIL PROTECTED]> writes: MF> So what's insufficient about: MF> print <<"EOF"; MF> Stuff MF> More stuff MF> Even more stuff MF> EOF Counting spaces, why make the programer work. Are those tabs or spaces? And it doesn't strip t

Re: RFC 111 (v1) Whitespace and Here Docs

On Wed, Aug 16, 2000 at 03:05:23PM -, Perl6 RFC Librarian wrote: > With a here doc print < the text of the here doc, is processed verbatum. This results in Here Docs > that either stick out in the code, or result in unwanted leading whitespace. > There are several FAQs that relate to this pro

Re: RFC 111 (v1) Whitespace and Here Docs

On Wed, Aug 16, 2000 at 03:05:23PM -, Perl6 RFC Librarian wrote: > =head1 ABSTRACT > > With a here doc print < the text of the here doc, is processed verbatum. This results in Here Docs > that either stick out in the code, or result in unwanted leading whitespace. > There are several FAQs t

RFC 111 (v1) Whitespace and Here Docs

This and other RFCs are available on the web at http://dev.perl.org/rfc/ =head1 TITLE Whitespace and Here Docs =head1 VERSION Maintainer: Richard Proctor <[EMAIL PROTECTED]> Date: 16 Aug 2000 Version: 1 Mailing List: [EMAIL PROTECTED] Number: 111 =he