develooper Front page | perl.perl5.porters | Postings from March 2021

Re: Let's talk about trim() so more

Thread Previous | Thread Next
From:
B. Estrade
Date:
March 27, 2021 01:04
Subject:
Re: Let's talk about trim() so more
Message ID:
d8eed5d3-39bf-dc9e-3522-dffefcdb02e5@cpanel.net


On 3/26/21 7:58 PM, Christian Walde wrote:
> On Sat, 27 Mar 2021 01:53:54 +0100, B. Estrade <brett@cpanel.net> wrote:
> 
>> At the end of the day, it seems to me that the real motivation for 
>> this is to eliminate this idiom:
>> chomp($foo);
>> $foo =~ s/^ *//g; # or however YOU do it
> 
> Nope, the motivation is to replace this:
> 
> $a =~ s/^\s+//; $a =~ s/\s+$//;
> 
> Which is like 1600+ times on cpan. 
> https://grep.metacpan.org/search?q=%5C%5E%5C%5Cs%5C%2B%5B%5E%5C0%5D%2B%5C%5Cs%5C%2B%5C%24%7C%5C%5Cs%5C%2B%5C%24%5B%5E%5C0%5D%2B%5C%5E%5C%5Cs%5C%2B&qd=&qft= 

Okay; well in this case my personal preference is to see a trim that 
misbehaves as chomp does; even if it trims both sides. That boils down 
to affecting the value in-place - or rather not introducing another 
special case of explicit string manipulation that behaves differently 
than one the one provided; the rest remaining on that crusty old regex 
thing.

> 
> 
> That said, i also recommend asking the author, Scott, for his 
> motivation. :)

Okay, Scott? Inquiring minds would like to know :)

Thank you,
Brett

> 

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