Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:119099 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 14924 invoked from network); 8 Dec 2022 14:12:00 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 8 Dec 2022 14:12:00 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 6BC6A180544 for ; Thu, 8 Dec 2022 06:11:58 -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=-0.5 required=5.0 tests=BAYES_05,DKIM_SIGNED, DKIM_VALID,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_NONE, 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-il1-f176.google.com (mail-il1-f176.google.com [209.85.166.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 ; Thu, 8 Dec 2022 06:11:57 -0800 (PST) Received: by mail-il1-f176.google.com with SMTP id x11so786761ilo.13 for ; Thu, 08 Dec 2022 06:11:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=basereality-com.20210112.gappssmtp.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=wFrZktS4D5uqDNoU9JU9wBaGwpoGrGFFZc+hrKsP4AY=; b=TgJFGVE4RVk4wN5cwJjDzYCn7SxSqbonreiDfEodJDkm33PONFGbhj/m7TEniGM38F KlH6/DVgzdtKQKl4JN5awQ/baoM/THYOB1MkLMmuE20otOAXibzwIxh3FkkJekLrGDiD 4sv7Lg20CRcmWDV/hwjrLU4BGUqDVhInGKZA61Hfry9rvjchXBWuMjG9Y/el5KsDaua1 i8uRBsup+ZS1pV5tlo0GEgw/9L4hRErQL8cfZFTmHr9VoWfFM7hjJCuYiyNzQeoRcQJq fY9kVrehtJTpern6XFTgkeFltn+QKZTXRI35lZFkaagoITg5TH7zawU6ghmjToTLjLGQ RfMg== 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=wFrZktS4D5uqDNoU9JU9wBaGwpoGrGFFZc+hrKsP4AY=; b=23SsEMHe8sKJ9la8IFrRqQOoib/8gMa4RQFUjmSW9nEa7ZAHwD6X+yVS51b1uncvcC 7sKj/+zfyVBlKXvrOUSaMHekq4WQE887K4iP5WxxV+w+UJCVSD6/CEngbtZVyAheAssv fBc0O/FAv1hB8VWLYHiw/wKW/aOA+N2OCrabPsmMmDgbjuhs4LIU19FujS5X0TiYQ/LK QOg6G1GtFab5X3Q2S01sypYnbPJzeGIVvEZldZMgoicbPNbeEOwebh3yj0rx9DyN8oZc 1pinQeZb77LziFEr3jS/NQllMr1hyEKDXKCIiCcJO+57irtgwyMUs1nSUkijCbO/rBr5 XOIg== X-Gm-Message-State: ANoB5pn4zlMFGZGavoQRnWZMY5193btw8gV7iMkyfX1QVNN4TGjQQ7Xm 9fc69YZt7gGBOIqvIg0J3oAItmf4I8xp25MgfxIYeQ== X-Google-Smtp-Source: AA0mqf4qMubI/bJ8ph7AMHgkoo1rnyv8TmTJQVh5rP+MSUVs3I/uoSvNgnHGuKYKDrdCdaN8EZFKf++BArt+AsxHPkE= X-Received: by 2002:a92:c7c1:0:b0:300:ea36:d26c with SMTP id g1-20020a92c7c1000000b00300ea36d26cmr34801552ilk.299.1670508717226; Thu, 08 Dec 2022 06:11:57 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: Date: Thu, 8 Dec 2022 14:11:42 +0000 Message-ID: To: Derick Rethans Cc: PHP Developers Mailing List Content-Type: text/plain; charset="UTF-8" Subject: Re: [PHP-DEV] [RFC] More Appropriate Date/Time Exceptions From: Danack@basereality.com (Dan Ackroyd) On Tue, 29 Nov 2022 at 17:41, Derick Rethans wrote: > > I have just published a new "More Appropriate Date/Time Exceptions" RFC > > > Comments? > None of the 'Invalid serialization' errors tell the programmer who reads them what is wrong with the data. Unless the code was written in such a way that the data was in (and was logged) in the callstack, that would be a bit frustrating as someone might need to do quite a bit of work to find the data that was triggering the problem. Changing those to be specific error type, that included a method of 'getBadData' could make it easier to fix those issues. cheers Dan Ack