develooper Front page | perl.perl5.porters | Postings from February 2000

Re: proposed perlpod.pod patch

Thread Previous | Thread Next
From:
Brad Appleton
Date:
February 4, 2000 17:16
Subject:
Re: proposed perlpod.pod patch
Message ID:
200002050116.TAA24169@agogic.cig.mot.com
On Fri, Feb 04, 2000 at 04:56:34PM -0800, Jan Dubois wrote:
> But there is a very valid reason for allowing newline after a C<<

Yes - I noted precisely that very same reason later in the same message
(or maybe it was the very next one). I know that is a possibly common
occurrence. Its not enough to convince me that the newline must be
allowed however (even though I know it can happen - and that it would
likely happen to me at least as much if not more than anyone else).

> I hope you'll find the tuits to allow newlines after C<<  :-)

Its not the tuits that are my biggest concern, its the readability
(plain-ness) and also implementation performance. I know for certain
it will affect performance no matter how I implement it, because I
can't munge the newlines, and I need to count them. I also think one can
make a very good argument that its less plain to allow them in that
particular spot (though I can see the other argument too).

That doesn't mean I'm claiming it shouldn't allow the newlines, nor am
I refusing to do it. But before I do spend the tuits, I want everyone
to fully appreciate the pros and cons of it, and then come to an
p5p sanctioned decision before I work on it for a couple hours.

-- 
Brad Appleton <bradapp@enteract.com> http://www.enteract.com/~bradapp/
  "And miles to go before I sleep." -- Robert Frost

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About