Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:119171 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 268 invoked from network); 16 Dec 2022 13:54:50 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 16 Dec 2022 13:54:50 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 789CE18054D for ; Fri, 16 Dec 2022 05:54:49 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-1.1 required=5.0 tests=BAYES_00,SPF_HELO_PASS, SPF_NEUTRAL,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS30827 82.113.144.0/20 X-Spam-Virus: No X-Envelope-From: Received: from xdebug.org (xdebug.org [82.113.146.227]) by php-smtp4.php.net (Postfix) with ESMTP for ; Fri, 16 Dec 2022 05:54:49 -0800 (PST) Received: from localhost (localhost [IPv6:::1]) by xdebug.org (Postfix) with ESMTPS id D5CC310C0AB; Fri, 16 Dec 2022 13:54:48 +0000 (GMT) Date: Fri, 16 Dec 2022 13:54:47 +0000 (GMT) X-X-Sender: derick@singlemalt.home.derickrethans.nl To: Daniel Wolfe cc: internals@lists.php.net In-Reply-To: Message-ID: References: User-Agent: Alpine 2.23 (DEB 453 2020-06-18) MIME-Version: 1.0 Content-Type: multipart/mixed; BOUNDARY="8323329-1377742869-1671198466=:462551" Subject: Re: [PHP-DEV] Re: [RFC] Unicode Text Processing From: derick@php.net (Derick Rethans) --8323329-1377742869-1671198466=:462551 Content-Type: text/plain; CHARSET=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE On Thu, 15 Dec 2022, Daniel Wolfe wrote: > On 2022-12-15 8:34 AM, Derick Rethans wrote: > > Hi, > >=20 > > I have just published an initial draft of the "Unicode Text Processing" > > RFC, a proposal to have performant unicode text processing always > > available to PHP users, by introducing a new "Text" class. > >=20 > > You can find it at: > > https://wiki.php.net/rfc/unicode_text_processing > >=20 > > I'm looking forwards to hearing your opinions, additions, and > > suggestions =E2=80=94 the RFC specifically asks for these in places. > >=20 > >=20 > I love the idea, but we may want to think about using the terms > `trimStart` and `trimEnd` instead of `trimLeft` and `trimRight`. > Obviously, when the text in the parameter is in a right-to-left > language (e.g., Hebrew, Arabic), `trimLeft` and `trimRight` are going > to do the opposite of what one may expect from the names of the > functions. I know that identifiers like `ltrim` and `rtrim` are > longstanding conventions which everyone understands that they **really** > mean trimming from the start and end respectively, but this may be an > opportunity to amend the inaccuracy. That's an excellent point. And I've updated these names. cheers, Derick --=20 https://derickrethans.nl | https://xdebug.org | https://dram.io Author of Xdebug. Like it? Consider supporting me: https://xdebug.org/suppo= rt Host of PHP Internals News: https://phpinternals.news mastodon: @derickr@phpc.social @xdebug@phpc.social twitter: @derickr and @xdebug --8323329-1377742869-1671198466=:462551--