On Tue, Aug 08, 2000 at 08:53:30PM -0400, Dan Sugalski wrote:
> On Tue, 8 Aug 2000, Michael Mathews wrote:
>
> > Dan Sugalski said:
> > > > > * Do we even want to allow after-the-fact chomps, or do it
> > automagically
> > > >at read time?
> > > "Yes" is rather ambiguous.
> >
> > To clarify: "Yes", we (I) want to allow after-the-fact chomps. As you
> > alluded to yourself there are times when you may want to chomp strings that
> > were not read from files, therefore there would be no "read time".
>
> Just because we can do it now doesn't necessarily mean it's the right
> thing to do. Arguably anything you use chomp on that didn't come from a
> filehandle really ought to be run through a regex.
Unless you set $\, calling chomp is bad news anyway (in a module) because
it may not do what you want. And if you are going to write
{ local $\ = "\n"; chomp($str); }
you may as well write
$str =~ s/\n$/s;
Graham.
- Re: RFC 58 (v1) C<chomp()> changes. Mike Pastore
- Re: RFC 58 (v1) C<chomp()> changes. Mike Pastore
- Re: RFC 58 (v1) C<chomp()> changes. Michael Mathews
- Re: RFC 58 (v1) C<chomp()> changes. John Porter
- Re: RFC 58 (v1) C<chomp()> changes. Dan Sugalski
- Re: RFC 58 (v1) C<chomp()> changes. John Porter
- Re: RFC 58 (v1) C<chomp()> changes. Dan Sugalski
- Re: RFC 58 (v1) C<chomp()> changes. Johan Vromans
- Re: RFC 58 (v1) C<chomp()> changes. Dan Sugalski
- Re: RFC 58 (v1) C<chomp()> changes. Dan Sugalski
- Re: RFC 58 (v1) C<chomp()> changes. Graham Barr
- Re: RFC 58 (v1) C<chomp()> changes. Uri Guttman
- Re: RFC 58 (v1) C<chomp()> changes. Jonathan Scott Duff
- Re: RFC 58 (v1) C<chomp()> changes. Ted Ashton
- Re: RFC 58 (v1) C<chomp()> changes. Uri Guttman
- Re: RFC 58 (v1) C<chomp()> changes. Chaim Frenkel
- Re: RFC 58 (v1) C<chomp()> changes. Ted Ashton
- Re: RFC 58 (v1) C<chomp()> changes. Jonathan Scott Duff
- Re: RFC 58 (v1) C<chomp()> changes. Bart Lateur
- Re: RFC 58 (v1) C<chomp()> changes. Mike Pastore
- Re: RFC 58 (v1) C<chomp()> changes. Michael Mathews
