Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:118877 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 76065 invoked from network); 24 Oct 2022 10:59:42 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 24 Oct 2022 10:59:42 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 0CB45180044 for ; Mon, 24 Oct 2022 03:59:41 -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.8 required=5.0 tests=BAYES_50,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_ENVFROM_END_DIGIT, FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2, 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-qk1-f176.google.com (mail-qk1-f176.google.com [209.85.222.176]) (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, 24 Oct 2022 03:59:40 -0700 (PDT) Received: by mail-qk1-f176.google.com with SMTP id z30so5780935qkz.13 for ; Mon, 24 Oct 2022 03:59:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=g34RTzI6W/W69KPnKSfIq/WLGwAex7UgLO1Bw7OA3UU=; b=plq/CDbk5g6Z1BK9GZ2OJWhXFYK1vLKRS5zWDxCFwyHR3/A22wsFAedTvHAhJtgODL n4qsxaKQyEBQHsgJdMgSA2q6xL94os2ZHlBCxeESyj8ani7cRITZV9RiXydCe1L/gYbd d94QDtH5MjGfdyg1rUOVvB453PYYe8Pq/ikrPYquwJOx+gaWsu35/fyhL/duaEnjpfAp f5eFAwKLsj3YshkXBqORR1P441BwvL0MK1nnk/T76XX5C/Yf82+wVE7jLcgXgSe0ycGJ rwTA7GOLubPgIsW6aAH6+v/VMUGiB2bOkqBlHzDGxFnFUW/YJAjwQyg/yI71i8KEYMah wn8A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=g34RTzI6W/W69KPnKSfIq/WLGwAex7UgLO1Bw7OA3UU=; b=LjMQMF+20V1XiQtfqbPyBBxv9sjM9VlOLxQRZptZ7ro2Ndtl0p/9FBxarMDGzXi5EW oY28KUTM/TRPmddLO6KdrqOttpiZUBY64DRBfK4fys4qVrRdnZcCxCfyZ8fpFv53gGng wwXXSbvtHgr9GLA2iTQ3EgoypWTriFWHuqVvcIMIU8s7I2tZB44965qnJ1KehWihWFdq 8hdlf0ufMyl8mIMX/MrQ8wYBrcY4yWcvlYNssjNSr4qNnqkA2ugHbGDN1aD9dy2mVtMr q9LLnWVgff64ZKH+YEqPaa1C1AIvItXck5yzJmLZO7tbphW0GnjLS6X9XcF7UIMEmNxB aySw== X-Gm-Message-State: ACrzQf1F8sGRafZe/eECB/Mr76G7PtmYoXWi8I6ZmYUHP2nCr6ikbQrn ycj1c9Cgzasy6opWZThJg81u6T62jfvrR4AlcmGsAMsJ X-Google-Smtp-Source: AMsMyM7Z7PIK6yARy3S23Zn4V/jzX2L60Smk2Ns2fRiR873Gs3zcOmp5rLxZGEzqbgBMY3fctpcjYCDnhJupIMykpgY= X-Received: by 2002:a05:620a:4398:b0:6ee:be9f:435c with SMTP id a24-20020a05620a439800b006eebe9f435cmr22379812qkp.35.1666609179691; Mon, 24 Oct 2022 03:59:39 -0700 (PDT) MIME-Version: 1.0 References: <20221024045645.00bfc0d2@platypus> <870F98D7-A5D2-48EB-B992-5B4EDDD1B1DA@cschneid.com> In-Reply-To: <870F98D7-A5D2-48EB-B992-5B4EDDD1B1DA@cschneid.com> Date: Mon, 24 Oct 2022 11:59:29 +0100 Message-ID: To: PHP Internals Content-Type: multipart/alternative; boundary="000000000000228ce505ebc5b039" Subject: Re: [PHP-DEV] [RFC] [Discussion] SQLite3: remove warnings, move to exceptions From: tekiela246@gmail.com (Kamil Tekiela) --000000000000228ce505ebc5b039 Content-Type: text/plain; charset="UTF-8" Hi, I don't think we should be removing such large chunk of functionality in a minor version. If you want to change the default to throw exceptions, that's ok. But I wouldn't remove the method in 8.3 or 8.4 and only remove it in 9.0. What is the advantage to removing the Warning mode? Regards, Kamil --000000000000228ce505ebc5b039--