Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:110405 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 75711 invoked from network); 7 Jun 2020 06:03:40 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 7 Jun 2020 06:03:40 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 8E7DD1804B7 for ; Sat, 6 Jun 2020 21:46:45 -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.4 required=5.0 tests=BAYES_00, FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM,HEADER_FROM_DIFFERENT_DOMAINS, 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-pj1-f67.google.com (mail-pj1-f67.google.com [209.85.216.67]) (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 ; Sat, 6 Jun 2020 21:46:45 -0700 (PDT) Received: by mail-pj1-f67.google.com with SMTP id h95so4568384pje.4 for ; Sat, 06 Jun 2020 21:46:44 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=OzRsgRsR6QGaOQdEAugMb5oE/h0YULNJZ3aZDiAGn9g=; b=YleOzxEI/7Yb2/arpdR0TjD/3e2VUH016E0CcwT9J0ZPQxX9ssg5bUsvVsOQ2tR9Kb ifexPNS4MOz7cTNEmzNjkCL0YUmVmFM/+/hoK9XkKe9ONuqml9D5dT5VECo7GuA5p04R 9+m8TsbYqa9HgK71546i32XbtHpPKKAG7KGbwGVUV8mgV0/4VNrTxH2IEXHGmPlGAILL 6nsylKEAxIYzJ9GAHlm/EnjyibgzAs8uzlVHrX7d1p0QsNdSXpWX2ZOtAejtAOMHN5nO Hac61b9zRwQo39YjXtsxykVL8ATf230LnTgCGrBW9Qj991Whv90Cj76qfz1Avool1BJM Ofeg== X-Gm-Message-State: AOAM533nyhqsbOOJLBawFHTKS9H6f1hF0iz5TnAk4LRD2jZCV+gYriv9 On+WX/oKH8+A4fjlVNR+i86btKL92mvrF34NNG8= X-Google-Smtp-Source: ABdhPJwNCabNPZIkQgI0x8VwjhG7KxraB+iYWCv/xu00tmrZXXLhd1HdqfVTVwnric94w486KHXZgxQXQPm1FIrDTio= X-Received: by 2002:a17:902:6906:: with SMTP id j6mr16567526plk.261.1591505197312; Sat, 06 Jun 2020 21:46:37 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Sun, 7 Jun 2020 07:46:27 +0300 Message-ID: To: Theodore Brown Cc: Nikita Popov , Nicolas Grekas , PHP internals Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] [RFC] Deprecations for PHP 8.0 From: kalle@php.net (Kalle Sommer Nielsen) Den s=C3=B8n. 7. jun. 2020 kl. 05.58 skrev Theodore Brown : > So while I understand the desire to make upgrades as easy as possible, > I'm not convinced it's a good idea to delay these deprecations for > a later release. At the very least if deprecation is likely the PHP > manual should say something about it. I agree with this and feel very strongly about it, we should not delay deprecations since they can be disabled on a configuration level by removing the E_DEPRECATED bits from error_reporting anyway. Allowing our users to know at the earliest possible moment when something is going to be deprecated allows userland to have a larger time for upgrading as these warnings about certain behavior will change many years from now, but old behavior is still in effect. --=20 regards, Kalle Sommer Nielsen kalle@php.net