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

Re: trim vs trimmed revisited

Thread Previous | Thread Next
From:
Yuki Kimoto
Date:
March 1, 2022 03:58
Subject:
Re: trim vs trimmed revisited
Message ID:
CAExogxOiXx3+5YYitXnLr4e2izaO-WmV-4JzsozA+sJya+tmow@mail.gmail.com
2022-3-1 12:54 demerphq <demerphq@gmail.com> wrote:

> On Tue, 1 Mar 2022 at 04:49, Yuki Kimoto <kimoto.yuki@gmail.com> wrote:
> >
> >
> > 2022-2-25 16:35 Martijn Lievaart <m@rtij.nl> wrote:
> >>
> >> Op 25-02-2022 om 02:41 schreef Yuki Kimoto:
> >>
> >>
> >> 2022-2-25 0:55 Karl Williamson <public@khwilliamson.com> wrote:
> >>>
> >>> On 2/23/22 21:40, demerphq wrote:
> >>> > Virtually every other programming language uses "trim"; that should
> be a
> >>> > good enough reason for us to use it too.
> >>> >
> >>>
> >>> I am persuaded by this
> >>
> >>
> >> Me too.
> >>
> >> Perl used to be the king of programming languages, but now it's no
> longer the king.
> >>
> >> It makes sense to adopt the words we are familiar with in other
> programming languages.
> >>
> >>
> >> Note that I prefer trim over trimmed too, but not because of this
> argument. Looking at guidance from other programming languages is fine, but
> not because Perl must follow them because it's no longer king of the hill.
> If that is your argument, you should start using that other programming
> language instead of Perl.
> >
> >  I want to continue to use Perl even if Perl is no longer king of the
> hill.
>
> Lets just leave out "king of the hill" discussions from the list huh?
> It just *isn't* helpful as a way to reason about perl changes.  I
> think I know what you mean, and I think I agree, but it is ambiguous
> at best, and pushes people's buttons at worst.
>
>
OK.

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