Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:119048 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 70538 invoked from network); 28 Nov 2022 16:48:12 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 28 Nov 2022 16:48:12 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 1DA1A180087 for ; Mon, 28 Nov 2022 08:48:12 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,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-f45.google.com (mail-ej1-f45.google.com [209.85.218.45]) (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, 28 Nov 2022 08:48:08 -0800 (PST) Received: by mail-ej1-f45.google.com with SMTP id b2so11062226eja.7 for ; Mon, 28 Nov 2022 08:48:08 -0800 (PST) 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:message-id:reply-to; bh=mlsdb8r90I3QOD8kIU7I0mKLxL/aA++ufm07GMY6zbQ=; b=V6tLy5RVWoObEVWsUNiQD7iOrfhOL7Y/IlYtU8NtGAE+KD/U+Hgo/x1XHrazbiqYp0 UmrmBF4Q1xZvo8cCEU1DWShawBIw0qvPXN4EPMNOQung8VEZrAYXT2kdsHcFI2F3OUgq WgyYbZqCbitRBx7OKleXO9xVM4e6x2JWJpewqZKi/aOvBk3ADMuU9I1TX7Ju3ZntWZNr 7QkiGhKF719KQRnC7OttP3VqjL0cMl+QJmakmcuum4df3iRT8d22Xs3Eg/iqPwN3uNq/ HxtndgV4dx5doFDrIDh73K5CxQPdVExdTwEPcAVsvgzJnVjGZJqNLJkb4ZDgrKWoWEpi f94A== 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:message-id :reply-to; bh=mlsdb8r90I3QOD8kIU7I0mKLxL/aA++ufm07GMY6zbQ=; b=gdZntNiQKpfRtKo4fOr6eJ+vAtdGa2lmtchC+oH/Zde2ji0zd4hEa+qT9R1H4rN/5d FrEraxSFqTNImFBPqNN1UnoZ+lOEoSgjGOW5Z/G0P2tnWVxdgribLTY1ptjiCisJugb7 v35J6MRV1Bi9i8L+fjO19wIpkmdfd9EZLLZj5B0iPJcGurB+9ilpkBxMb5aHbG/ldCsE b3DmHZAwqGyDAKSSxo+YJHJJP7x39cCAGI/2wclhikC3s580DQHjY1uA3m7tvb3lwMiD PKg+bCZW579dysu4zjwaxRJZ9vLGl1939mTU0xhH6L44sFRokRc7GGVJt7r1VDT6L7O2 pb1w== X-Gm-Message-State: ANoB5pnDnkAWWOfhghVhi1/sF31h6AAPkwOGnrA1YdvAHR4FB8u27ARh 86Tq9CG2yNyljTqxv041eYemtr4I/mxBXjXvZ6U= X-Google-Smtp-Source: AA0mqf69onc7v6fXxj5ZtRZ0MMqmjrsf14IXHsy8Nvo5vfoCtj95Ipf85Xi2h99aqmNswFjQftKdgnLQJs6wbO8uxmA= X-Received: by 2002:a17:906:805:b0:78d:8267:3379 with SMTP id e5-20020a170906080500b0078d82673379mr43393056ejd.415.1669654087152; Mon, 28 Nov 2022 08:48:07 -0800 (PST) MIME-Version: 1.0 References: <9b74bcf3-9e0a-bf41-ef2e-d47948f815f8@gmx.de> In-Reply-To: <9b74bcf3-9e0a-bf41-ef2e-d47948f815f8@gmx.de> Date: Mon, 28 Nov 2022 16:47:55 +0000 Message-ID: To: "Christoph M. Becker" Cc: Derick Rethans , mickmackusa , PHP Internals List Content-Type: multipart/alternative; boundary="000000000000c3379e05ee8aa2b2" Subject: Re: [PHP-DEV] Remove warning when parsing datetime with + symbol? From: dragoonis@gmail.com (Paul Dragoonis) --000000000000c3379e05ee8aa2b2 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, 28 Nov 2022, 16:32 Christoph M. Becker, wrote: > On 28.11.2022 at 16:50, Derick Rethans wrote: > > > On Thu, 24 Nov 2022, mickmackusa wrote: > > > >> Can anyone explain to me why it is desirable/beneficial for the DateTi= me > >> class to store a warning that trailing characters were ignored while > >> parsing a date/time string with the + symbol in createFromFormat()? > > > > I have no idea why I decided that was a good idea back all these years, > > and I'm perfectly happy to remove that restriction from PHP 8.3 > > forwards =E2=80=94 it's too late to do that in PHP 8.2 now, as it's bei= ng > > released next week. > > That would appear to consitute a BC break. From the docs: > > | If this format specifier is present, trailing data in the string will > | not cause an error, but a warning instead > > This can be used to parse the date (without the +, parsing may fail), > but still be able to return a message about ignored characters to the use= r. > We are allowed to break BC in minor version upgrades, Chris. We can allow this is 8.3 I think, rather than waiting for 9.0 What do you think? > -- > Christoph M. Becker > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: https://www.php.net/unsub.php > > --000000000000c3379e05ee8aa2b2--