On Fri 15 Sep, Michael G Schwern wrote:
> On Fri, Sep 15, 2000 at 06:38:37PM +0100, Richard Proctor wrote:
> > 1) << removes whitespace equivalent to the terminator (e) this is largely
> > backward complatible as many existing heredocs are unlikely to have white
> > space before the terminator.
> >
> > 2) <<< removes whitespace equivalent to the smallest whitespace (d)
> >
> > or are these the options that will satisfy everybody [no but its worth a
> > try]
> >
> > 1) << Does just what it does now
> >
> > 2) <<< implements (d) or (e)
>
>
> I'd say:
>
> 1) << does what it does now mod RFC 111 (ie. you can put whitespace in the
> terminator, but it doesn't effect anything)
I was assuming that the terminators changed ala RFC 111 whatever happens
>
> 2) <<< does (e).
These are equivalent to my second set of options
>
> 3) distribute a collection of dequote() mutations with perl.
As a module presumably
>
> 4) mention the s/// tricks in the documentation (<<POD =~ s/// seems dead)
>
Yes.
> > [[there is still the tabs debate however]]
>
> Tabs are easy, don't expand them. Consider them as a literal
> character. This assums that the code author is going to use the same
> keystrokes to indent their here-doc text as the terminator, about as
> safe an assumption as any for tabs.
>
> Maybe I'm being too simplistic, I don't use tabs anymore.
>
Yes you are, the problem comes with mixing editors - some use tabs for
indented material some dont, some reduce files using tabs etc etc. [I move
between too many editors]. Perl should DWIM. I think that treating tabs=8
as the default would work for most people, even those who set tabs at other
values as long as they are consistent - a "use tabs 4" could be used by them
if they want to get the same behaviour if they mix tabs and spaces.
Richard
--
[EMAIL PROTECTED]
