Re: [RFC] [VOTE]

From: Date: Wed, 29 Jul 2026 16:49:35 +0000
Subject: Re: [RFC] [VOTE]
References: 1 2  Groups: php.internals 
Request: Send a blank email to internals+get-132126@lists.php.net to get a copy of this message
&gt; Nora&nbsp;isn't&nbsp;on&nbsp;the&nbsp;list,&nbsp;but&nbsp;she&nbsp;points&nbsp;out: &gt; &gt; The&nbsp;text&nbsp;for&nbsp;the&nbsp;metaphone&nbsp;deprecation&nbsp;isn't&nbsp;fully&nbsp;right.&nbsp;It&nbsp;lists &gt; "linguistics"&nbsp;as&nbsp;a&nbsp;replacement&nbsp;package,&nbsp;but&nbsp;that&nbsp;one&nbsp;actually&nbsp;uses &gt; php-src's&nbsp;metaphone&nbsp;internally&nbsp;too.&nbsp;So&nbsp;it&nbsp;is&nbsp;affected&nbsp;by&nbsp;the &gt; deprecation,&nbsp;not&nbsp;a&nbsp;replacement. &gt; &gt; As&nbsp;demonstrated&nbsp;by: &gt; &gt; <?php &gt; require&nbsp;'vendor/autoload.php'; &gt; \Linguistics\Phonetics::metaphone('foo'); Thanks for noticing. Worth noticing that only the Phonetics::metaphone function use php's metaphone(). Also, that function is barely a bridge for applying existent functions of PHP. All other advanced algorithms ain't affected by the metaphone deprecation. My point in deprecating it is to stop using ancient metaphone algo as a whole. And Linguistics offers loads of implementation. So this is still a replacement. However, I do see the reason to make this clear in the RFC text. I also forward this to Nora. - Weilin

« previous php.internals (#132126) next »