Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:116176 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 12026 invoked from network); 26 Sep 2021 13:48:36 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 26 Sep 2021 13:48:36 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 6C76D1804E1 for ; Sun, 26 Sep 2021 07:30:50 -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_20,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 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-ot1-f42.google.com (mail-ot1-f42.google.com [209.85.210.42]) (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 ; Sun, 26 Sep 2021 07:30:49 -0700 (PDT) Received: by mail-ot1-f42.google.com with SMTP id x33-20020a9d37a4000000b0054733a85462so20612848otb.10 for ; Sun, 26 Sep 2021 07:30:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=rtpSGn7CyOYonNF0aeYe9pEXCyhns8qhZHs6YQu9dO4=; b=m6Wbp9YRNZ2Qx7WUA8PBNlYZVgKyIXd57iYLFyE3r+MeRNxilQmtqYmx8IXWtcif8t XwvoxwSeXd7YJTnzOgahQ7G5Jt/ut+hzeynUOJoF/IRfMP20hCdytCTniZDQSc0tsYkl hQ/4PBiGoCt+NLA9XI1U/zSS2xOskKjty0mXk7G4xh3+L/qIz+6TY3FzTT1suK6SD9+u SGxZtQgak+qPRMHHAwX/nNT9EQabgINan1GTe0xSC7fNtXyPC5G3d0D9w8qGgfx0uRAP j4GKRY/M6lDygE8LlzmB8JYpipNUMpebsX7n1aIRyeOLcdfTnHqPDCgXkuJMAgkKvf/I kxCw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=rtpSGn7CyOYonNF0aeYe9pEXCyhns8qhZHs6YQu9dO4=; b=x/bOFJlehpA9ksNpVDa1bfW9X/Bd4nOBeJ+Ex2o3Bt2TeT86C2SekitOxY8x3eXzhX Q6saPwTZJzbq+ULrWgxWrccovORUrj4YJz/BIE/U7KMgJWfabvgLN6NwMKEctXX3DUzE 64rRgyXeh2wtSkkETmrJKWjKw7VwAoOkL0j5XISpAhtMNs2tufQhITpxzJ6pPocVIfgL pJyBSWXekuRzKrup4pOmrnScYtxiSkTUcKFWFWfyu7rfAK8Yj4qz+aN7TVIyIMAQP1Fg vM54wr3rprgFywF6EjytJ8LoLWhzYEJM1HLZOAFIWqjARRZg+RHiQm5uWMX9rXEGS8u9 d5sg== X-Gm-Message-State: AOAM530hSJnhrRl976Z+56RG6f/rRH1aBn+oS/mI9fDLON+ODxKIOaBY IbDGqvQDzGfNJFdiQd6halsEJfemifaZMY2ICRUGpo+ukqY= X-Google-Smtp-Source: ABdhPJxeHcCEyTTr5xyeodU+PMjXDaQhXRGkoJEZwGcm48aZPKUQKM2VI0/8fiz+yVUE6LNx79SNAglL48HJ84pHXKQ= X-Received: by 2002:a9d:2f24:: with SMTP id h33mr13596797otb.254.1632666649318; Sun, 26 Sep 2021 07:30:49 -0700 (PDT) MIME-Version: 1.0 References: <12f54268-1a63-ad10-de01-ee03a6845ed9@seld.be> In-Reply-To: <12f54268-1a63-ad10-de01-ee03a6845ed9@seld.be> Date: Sun, 26 Sep 2021 21:30:37 +0700 Message-ID: To: Jordi Boggiano Cc: PHP internals Content-Type: multipart/alternative; boundary="000000000000ab5a2505cce6d3e1" Subject: Re: [PHP-DEV] BC breaking changes in PHP 8.1 From: pierre.php@gmail.com (Pierre Joye) --000000000000ab5a2505cce6d3e1 Content-Type: text/plain; charset="UTF-8" On Sun, Sep 26, 2021, 7:42 PM Jordi Boggiano wrote: > > > I'm surprised that is_resource() returns false for resource objects, > > does anyone knows why it wouldn't return true in such case ? > > > > This is a very weird behavior, I'd expect it to return true, moreover > > this is the most annoying detail of this BC break, in my opinion. > > > > I have lots of code using is_resource() but I usually don't bother > > checking for type (maybe I'm doing it wrong). But I'd also expect > > get_resource_type() to be deprecated somehow and return > > backward-compatible values for converted resources to objects. > > Right, having is_resource return true for resourcey objects would have > prevented all resource-related errors I ran into with php8.0 migration I > believe. That'd be a welcome improvement/fix for 8.1. > that was proposed but purity won if I remember correctly. That's kind of defeat the initial goal (attempt) of yearly releases. Now I feel like we introduced more, small or big, bc in minor releases in the name of purity. That counter balance the yearly release with no bc from a migration pace pov. best, Pierre > --000000000000ab5a2505cce6d3e1--