At 02:29 PM 8/8/00 -0400, Michael Mathews wrote:
>Dan Sugalski said:
> > Which brings up the questions:
> >
> > * What about scalars that didn't come from filehandles?
> > * Should the chomp function use the filehandle's current separator, or the
> > one in effect when it was read?
> > * Do we even want to allow after-the-fact chomps, or do it automagically
>at
> > read time?
>
>YES, of course!
That last was an "A or B" sort of question. Yes is rather ambiguous. :)
> > * Is it worth the extra space per scalar to store the record separator (or
> > a pointer to the filehandle holding the record separator)?
> >
>
>What about a
> chomp($foo, '\r\n');
> # or
> chomp(<FH>, '\r\n');
>syntax.
Looks an awful lot like:
s/\r\n//;
to me...
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
- RFC 58 (v1) C<chomp()> changes. Perl6 RFC Librarian
- Re: RFC 58 (v1) C<chomp()> changes. Bart Lateur
- Re: RFC 58 (v1) C<chomp()> changes. Ted Ashton
- Re: RFC 58 (v1) C<chomp()> changes. Segher Boessenkool
- Re: RFC 58 (v1) C<chomp()> chan... Ted Ashton
- Re: RFC 58 (v1) C<chomp()>... Larry Wall
- Re: RFC 58 (v1) C<chomp()... Larry Wall
- Re: RFC 58 (v1) C<chomp()... Dan Sugalski
- Re: RFC 58 (v1) C<cho... Michael Mathews
- Re: RFC 58 (v1) C<cho... Dan Sugalski
- Re: RFC 58 (v1) C<cho... Michael Mathews
- Re: RFC 58 (v1) C<cho... Uri Guttman
- Re: RFC 58 (v1) C<cho... Ted Ashton
- Re: RFC 58 (v1) C<cho... Uri Guttman
- Re: RFC 58 (v1) C<cho... Ted Ashton
- Re: RFC 58 (v1) C<cho... Mike Pastore
- Re: RFC 58 (v1) C<cho... Mike Pastore
- Re: RFC 58 (v1) C<cho... Michael Mathews
- Re: RFC 58 (v1) C<cho... John Porter
- Re: RFC 58 (v1) C<cho... Dan Sugalski
