Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:115013 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 35857 invoked from network); 22 Jun 2021 09:19:07 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 22 Jun 2021 09:19:07 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 9D6631804C3 for ; Tue, 22 Jun 2021 02:37:20 -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=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_NONE autolearn=no autolearn_force=no version=3.4.2 X-Spam-Virus: No X-Envelope-From: Received: from mail-qk1-f169.google.com (mail-qk1-f169.google.com [209.85.222.169]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Tue, 22 Jun 2021 02:37:20 -0700 (PDT) Received: by mail-qk1-f169.google.com with SMTP id g4so36555974qkl.1 for ; Tue, 22 Jun 2021 02:37:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=newclarity-net.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=cjlaWvFUNvOScaS0IpQNeVdXA+EakiAbtD55IAuBWGg=; b=EQYoxOsUiJ9gyZF1k409ad+FTxKal9WQpG8VeHK24RX3rVEzQGEk1hX1UZkL3ZNGYS lZKpAkg1Fmh5L0nUBZUsuiievskqHC1lp6Apn4Wa9j3djOSfdl5sqEhiyn2MZxyqeUrp nb8WVWI2lwpQP863jxrQrweQOvNgGFilHanD4Bpb6c/QrXgTcLqUSTwjmlx4tBbLU4Xc iAlOMTmpEViI6iOW5cPWDWfLASxMmvnVOJSsCZX51wx5Iif80OFnpSCzC6SnIjyjv6ty nkddpiiflupJatqN07rvuWZwq1Rnr2IgyFxiBwV2k3B7CWdk2+ye4puMwd+Mwnx4/dLt VoCg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=cjlaWvFUNvOScaS0IpQNeVdXA+EakiAbtD55IAuBWGg=; b=JxI5/05ZBmlzqDZeqD+CXw+shUVuQFrU5feGHYb/pkCWZT1RUdZRvM0FJO1vJZVJsZ bB0Wb0QyICXGKSHtMD/GNdI119PTfT+AOeQbesjnn5NVID1xu6tmmQvMwEUrsxrNjv+i bvRO7I8xwwQJnQ3KLn6mHtPQ0NEMq/TGAr56GU9saw/p6NlK3XUSsTI8U1AaqHHLwHH6 koQOSneQzDYtZOgeP/k8FH8/fAJsjPqy9TKbqcHAxJt8A+iUxNxcoloFaG+j7Lnl7sQP QmAxskIqT1lAE0EtuOnFkIuZLz9WtjSQJVUpbsUnwuh26Tuc0JWuzvFbSuUayIWoXSwI xREQ== X-Gm-Message-State: AOAM532lRap7ijoYbrtqmzmJTc95UTrqMSqR8DkWHF7stIuKEgeHCaAS NW1FdObhns14aVFvjU/m/Ktl7Jo5CQFk1zwl X-Google-Smtp-Source: ABdhPJwYZ3gFXZ1tndmrYUx2bKgjUcRPXBJHSeGywttc5f3HX7G5WVnmW1IArimYFduV2F60XCl4Ig== X-Received: by 2002:a37:89c5:: with SMTP id l188mr3241856qkd.27.1624354637811; Tue, 22 Jun 2021 02:37:17 -0700 (PDT) Received: from [192.168.1.10] (c-24-98-254-8.hsd1.ga.comcast.net. [24.98.254.8]) by smtp.gmail.com with ESMTPSA id x11sm7529711qki.23.2021.06.22.02.37.17 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 22 Jun 2021 02:37:17 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\)) In-Reply-To: Date: Tue, 22 Jun 2021 05:37:16 -0400 Cc: PHP internals Content-Transfer-Encoding: quoted-printable Message-ID: References: To: Dan Ackroyd X-Mailer: Apple Mail (2.3608.120.23.2.7) Subject: Re: [PHP-DEV] [RFC] is_literal From: mike@newclarity.net (Mike Schinkel) > On Jun 22, 2021, at 5:28 AM, Dan Ackroyd = wrote: >=20 > On Tue, 22 Jun 2021 at 10:25, Mike Schinkel = wrote: >>=20 >> Should(n't?) PHP add a basic SQL builder class that can be extended = for special cases, e.g. different flavors of SQL? >>=20 >=20 > No. Or at least not yet. >=20 > This type of thing is much better done in userland, where the api can > evolve at a fast rate, rather than being limited by the fixed release > schedule of PHP. >=20 > If, after people had settled on a good api, someone could make a > strong argument for adding it to core, it could be evaluated then. Sure. But that is not inconsistent with what I was asking/proposing. =20= There would be a benefit to collectively working towards to = defect-standard solution rather than leave it to the chaos of userland = to come up many different approache, even if initially in userland. Even a PSR might be appropriate, but I tend to think the = interface-centric approach only works well things there the benefit it = interoperability and not when the benefit is implementation. -Mike=