Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:118731 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 76107 invoked from network); 3 Oct 2022 10:29:57 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 3 Oct 2022 10:29:57 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id D6279180211 for ; Mon, 3 Oct 2022 03:29:56 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-0.2 required=5.0 tests=BAYES_40,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,HTML_MESSAGE, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE, SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS15169 209.85.128.0/17 X-Spam-Virus: No X-Envelope-From: Received: from mail-ej1-f53.google.com (mail-ej1-f53.google.com [209.85.218.53]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Mon, 3 Oct 2022 03:29:53 -0700 (PDT) Received: by mail-ej1-f53.google.com with SMTP id z23so4396362ejw.12 for ; Mon, 03 Oct 2022 03:29:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date; bh=6nLcpRb3g893ZSf1miZTLuLm7DGZrgCg175XfMOJv6U=; b=l7HUQTDPvvyQnfQNMI62ThdzbjyYXvwtLSKCmqyHAt+CkpifsQ6KkkV/SuaV0OpVDr Wx2DMOtGh9jHyz53H6eTRHCyzAYv/5wnWkP3ah1I3OrWGsm06pbYxqoGL3mYOcvCxupO AlF670rRC9lD2KbvAFZCB1jFTgolyKZPVK7uvm3Q6YqoXMAzcsc+4raectls1PnFBZNq mA2sM3Bptr91WsJZbVAUEdc7/1x9Idhb7uFqoCfuq9oogDZslO7xWvinC73EZe/72XOI 6I6US6zPUViB2bOEUi2AUmRN/cxIo7c7uTGPVUrPgMMRotfTjXkM9gHtwzSl/zCFTnyU 3yPA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date; bh=6nLcpRb3g893ZSf1miZTLuLm7DGZrgCg175XfMOJv6U=; b=oBDYA1PQydHAIfyrzrLQI26Wg4jxE4HjyrcG5vFX9KrIaF7d3EkpMm3RqfCElUA++/ mbwJyaYgY2g+/NzXuN8KEP6EqfM1HzwtvRPFsZg34GloOed5qOhS6sdYcMajYPSonmrm F4rJ1JWwn3qTJkunneIJRj+IUXfya9xI1+dgDV4kLY7YmIK6mGgnagvMMNN3FLo791RZ D3YL3dqlInT6SFG6QJ/IG5TKmSoZQe4TEOr7zhk6RsChnTeI12nmlcVKaaZynocryzAQ c7cV9vy1pcFPw1tTqDuNWmW30ossUwJyQz1bVnX1GmqmPo8Kt9Xv8bduZKVnp0GVczJM CAvQ== X-Gm-Message-State: ACrzQf3GV/NAXlasr3+iOe0r/lh2EhksVC+lRt9Ia5FsmmZaZ8W7HCny cXOHu+a09UqO/OAfaEe0DwmOg75GviGcyv/8UnDylJhN X-Google-Smtp-Source: AMsMyM6e0nyU0i0MYWXyE/Xsj/h3JeFLnTK4dhDANrKWFwCZsRw5XEmJqfAy/ttSIs5qOsg1UuAopBjQ6uFRy0RLA/U= X-Received: by 2002:a17:907:a064:b0:78c:1511:a3cd with SMTP id ia4-20020a170907a06400b0078c1511a3cdmr1772623ejc.203.1664792991877; Mon, 03 Oct 2022 03:29:51 -0700 (PDT) MIME-Version: 1.0 References: <0cfb9a7b-1168-42ef-ae1a-bdc72210de43@app.fastmail.com> In-Reply-To: Date: Mon, 3 Oct 2022 13:29:40 +0300 Message-ID: To: David Gebler Cc: Larry Garfield , php internals Content-Type: multipart/alternative; boundary="000000000000e7d21605ea1ed2b5" Subject: Re: [PHP-DEV] Sanitize filters From: maxsem.wiki@gmail.com (Max Semenik) --000000000000e7d21605ea1ed2b5 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable =D0=BF=D0=BD, 3 =D0=BE=D0=BA=D1=82. 2022 =D0=B3., 03:18 David Gebler : > At a glance, I think all the examples mentioned in this thread have bette= r > existing alternatives already in core and could just be deprecated then > removed. But it's worth asking, is that what we're talking about here, or > is there a suggestion of replacing the filter API with a more modern, > object API? > Is there a compelling need to have this in the core, as opposed to Composer packages? The ecosystem has changed a lot since the original function was introduced. > --000000000000e7d21605ea1ed2b5--