Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:106268 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 29760 invoked from network); 24 Jul 2019 00:17:19 -0000 Received: from unknown (HELO mail-ua1-f54.google.com) (209.85.222.54) by pb1.pair.com with SMTP; 24 Jul 2019 00:17:19 -0000 Received: by mail-ua1-f54.google.com with SMTP id j21so17645696uap.2 for ; Tue, 23 Jul 2019 14:40:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=/g6x402oM0DWaCfHj6Tn+1SS93TkGMO1Z+0YLa85ScI=; b=A9xwQb8jzF4GG5yho9Q8L6KapZ56SUmV9QNbCFkDel7vR6w51VnQucvAnalM9OzNjI 3gqzOCTNs45+seOtY2FJuudrl6zGS4tAjAt2dRjX7IZx/lndc09iNxkyJLscBaKhJKg1 6e6G/Xz/EtyKbBYmFVkKn8iXiuh0ZaUIKA9hr2naDay1xs29DEyUErRevIqn3gUlc/9f /migpDahmZMJbglKUQmyKdtAeo1Xi5bLEMg/Dxb5nSCCaXCOyraznWDQmWN3sLQ1i+80 RidEZfgD5UcWcXNStiXP5YL4klTYTA24+mSv4vKjAHerQXjxgojPtbFpyNMuN4+dcVYE YFaA== 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; bh=/g6x402oM0DWaCfHj6Tn+1SS93TkGMO1Z+0YLa85ScI=; b=agd/gLGRd8Suoyn6KHa9lOsXn6hPB/iyHoSiubIRgL+fZfYYj2zDBHT+AQs7jOgYfU 7XswX1oJTwoN75CAEYC1WmDa7pUXmhkG6nFTBBoVGkavBjSbF3DGiW9usGLbblGkqTAL 4xzWRolzXtsRD4WBPKMqN71c77aj9AwKYdEmZRp03LRjU3jErAXRh9l4oDP02mV91Kzg KocUDB2uZTig+lye0Ax9mshu4E3omVZThq66Ds8EFaGLKXZgSlb0RMPYEKVemiUPSzUR 5Ic2TFxBPg742Z8gJ5sE7rMicZUBRiUDMhoPGHlQAxK/jfAN6V06JVTLcXp/WzbTO9lf 4sGg== X-Gm-Message-State: APjAAAWP96W5FVcv7tMn1MyzIA5zb1kWNtdtiJWzXC5RjO6QBajzdvks 9Hsfu3U8zJRHZ+NM6UAma+xiggm0/rLtv5c49OI= X-Google-Smtp-Source: APXvYqyq8rCvGiFPdLHJ/amBSabzkmMBwBOHWtOKzBXyBmY6+2zqm22RAGiF08N3HP28oO66dfz3acSYi9mZ/YXiXy4= X-Received: by 2002:ab0:7c3:: with SMTP id d3mr4764363uaf.131.1563918033606; Tue, 23 Jul 2019 14:40:33 -0700 (PDT) MIME-Version: 1.0 References: <5C8F3403-2972-467A-AFA5-347C09E5FA73@gmail.com> In-Reply-To: Date: Tue, 23 Jul 2019 22:39:57 +0100 Message-ID: To: Nikita Popov Cc: Rowan Collins , PHP internals Content-Type: multipart/alternative; boundary="000000000000d9dcc8058e600af2" Subject: Re: [PHP-DEV] [RFC] [DISCUSSION] Deprecate PHP's short open tags V2 From: petercowburn@gmail.com (Peter Cowburn) --000000000000d9dcc8058e600af2 Content-Type: text/plain; charset="UTF-8" On Tue, 23 Jul 2019 at 22:03, Nikita Popov wrote: > On Tue, Jul 23, 2019 at 9:10 PM Rowan Collins > wrote: > > > On 23 July 2019 18:54:48 BST, "G. P. B." > wrote: > > >The only point of contention of this RFC that I potentially see is the > > >removal in PHP 8.1 after short open tags being a Parse Error in PHP 8.0 > > >instead of it being removed in PHP 9 after it having had a whole major > > >version release cycle. > > > > Given that you've already predicted that this will be controversial, > could > > you provide some rationale for it? Unless there's a major burden in > > maintaining the parser error behaviour for a few years, waiting for the > > next major version would seem both safer and more in line with official > > versioning policy. > > > > As with deprecation itself, any violation of the "no breaking changes" > > rule, however slight, should have an explicit justification. If I had a > > vote, any RFC omitting such a justification would receive an automatic > "no" > > from me. > > > > I agree. I don't think there's a pressing need to do the "full removal" in > PHP 8.1 in particular, so it makes more sense to this in the next major > version (9.0), as usual. > > Nikita > Would you (George, Nikita) consider removing the details about the eventual removal of the feature from this RFC? We can run with the error for a bunch of releases / years, and see what happens. I don't see why we should necessarily decide now on something that might be 5 years or more away. --000000000000d9dcc8058e600af2--