Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:130054 X-Original-To: internals@lists.php.net Delivered-To: internals@lists.php.net Received: from php-smtp4.php.net (php-smtp4.php.net [45.112.84.5]) by lists.php.net (Postfix) with ESMTPS id 8C0301A00BC for ; Sun, 8 Feb 2026 13:55:49 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=php.net; s=mail; t=1770558954; bh=7CEKbi1KfHg5NX3HLSMC/Ank0ZzfjPcs7shy3wk47RQ=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=D0MO3hALH23y2apQpzJxRmH/0OaSJ8vUUxdJY7Jt9wnZNGe0DLcCEk3w8ZLvJQkhL sF3utS0gv8c7YKq+Yi21VLiI8XT0zo5CrDLIa5AoJ9m2/JlcTEKjY2vBkQAdw9SUTu 4EcqVnwVT42uEdB3ai4SD9Acr5YIm74JeIhHR767wn36NT0ljjjF4SSSRga02I6mtR beHXthx62B5/towYkdb086YPmsHK0rMvuzBLSIRZZdlOq1ywdo0SeZldDvig8KRCvn zwzcHgDehq6kuou2t1T47lzylmJoGDeBEqIuaNUFAuEPKSHGXaJsvhZyCiGNbNaB9p I9HiCXULMLMGA== Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 22FDE18004F for ; Sun, 8 Feb 2026 13:55:50 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 4.0.1 (2024-03-25) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=0.6 required=5.0 tests=BAYES_50,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,DMARC_PASS,SPF_HELO_NONE, T_SPF_TEMPERROR autolearn=no autolearn_force=no version=4.0.1 X-Spam-Virus: No X-Envelope-From: Received: from chrono.xqk7.com (chrono.xqk7.com [176.9.45.72]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Sun, 8 Feb 2026 13:55:49 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bastelstu.be; s=mail20171119; t=1770558942; bh=dbs3bCHyJQPz7wwF3midMC9y0PHHpwnA5cD21eftlg8=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type:from:to:cc:subject:message-id; b=WYZ7uWfPHYWWlD9s0MMXjARRtlP1hVAg/2z3SRnrjXXZR2QxVg5wYtYollp9fbSX8 xF9EkPH83+5NlnZtCIJQNjf3EZZUuwEzISvBFaLH1Ttwe3d8fPceDq6252ceEhfdPb o0N6u5dOGzuljR+z+kt+D4XS3ODBBbeU5mFnbBLIzqxBTxiLTZdkqkmu6FFLRfCrb0 sRI9/4ILvcOCZ+GJKgOf/2EpvbB402hVcDoKJkoeF4G8N0/kQ5efVfXFcQBnyR8GwN VQMUq9alzoaK1B0w99KzZQnSunemT2PZ7w9gktYe/55ON/WBa2KpmZeRiV1bIuaIhq ttrqkCXneAOsw== Message-ID: Date: Sun, 8 Feb 2026 14:55:37 +0100 Precedence: list list-help: list-unsubscribe: list-post: List-Id: x-ms-reactions: disallow MIME-Version: 1.0 Subject: Re: [PHP-DEV] [RFC] [Discussion] Prefix and Suffix Functions To: Barel , Ben Ramsey Cc: internals@lists.php.net References: <15b6506dc69bd13eceffd36375f83509@bastelstu.be> <20260206233458.6DEF81A00BD@lists.php.net> <20260207073732.D7BA81A00BD@lists.php.net> Content-Language: en-US In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit From: tim@bastelstu.be (=?UTF-8?Q?Tim_D=C3=BCsterhus?=) Hi On 2/7/26 09:21, Barel wrote: > I have added a new section to the RFC explaining the discrepancy about > parameter order for the _replace functions. I have also added a new > secondary vote to decide this order. Would appreciate it if someone could > confirm that this is all OK. For the secondary vote you'll need to define a tie breaker. I assume the ties are broken in favor of `$subject` last, since that's what the RFC uses in all examples, but it will need to be clearly stated. Personally I'm team “I don't think the functions are necessary, but if they are included, they should match str_replace()”. Best regards Tim Düsterhus