Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:65567
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.46 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAOfzkkz3DC+aVb4c73QHGRzZv=1z=nG4uexdJh2n8h3ATGBBOA@mail.gmail.com>
References: <CAOfzkkz3DC+aVb4c73QHGRzZv=1z=nG4uexdJh2n8h3ATGBBOA@mail.gmail.com>
Date: Sun, 3 Feb 2013 13:19:13 +0100
Message-ID: <CAEZPtU6UdX4uyR7tLomi==DNbmJduHoxa=qmb+dd2bJQKcoxjw@mail.gmail.com>
To: Karoly Negyesi <karoly@negyesi.net>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] Proposal for serious BC compatibility aka language versioning
From: pierre.php@gmail.com (Pierre Joye)

hi,

On Sun, Feb 3, 2013 at 12:36 PM, Karoly Negyesi <karoly@negyesi.net> wrote:
> Hi,
>
> So, if we are talking about PHP 6, then the opening <?php tag should be
> accompanied by the version it was written for, it was tested with and then
> the engine could switch to a compatibility mode for that version.
>
> Seems to me that this would solve the problem where a host can't upgrade to
> a more modern version for fear of breaking old code. Consequently, open
> source packages -- like Drupal I am deeply involved with -- can't use more
> modern PHP versions decreasing the "push" for hosts to upgrade. This is a
> devilish circle and it'd be great to break it.

We have been there, no chance to go back again with such tags.

Also the new release process RFC
(https://wiki.php.net/rfc/releaseprocess) solves the BC issues between
minor updates (5.4 to 5.5, or 5.3 to 5.4 f.e.). It is our and our
users role to explain that to their ISPs, admins, etc.

Cheers,
--
Pierre

@pierrejoye