Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:106457
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
	s=turbo-smtp; d=php.net;
	h=Received:Received:X-TurboSMTP-Tracking:X-Gm-Message-State:X-Google-Smtp-Source:X-Received:MIME-Version:References:In-Reply-To:From:Date:X-Gmail-Original-Message-Id:Message-ID:Subject:To:Cc:Content-Type;
	b=NnvwT4R1nH7eVXURH13ZfVxVNh3SuQ2biXw+G09sU4EnEVX2SnpdFIKcM1t3Q/
	Dt1Fye/3kLyeqMGdPFEfs8VFbZ1al9k7u8dbt0hJjUBCoOfbwSX+bsSI1yqrtF37
	OeAmJjZ/72Lhf3NCOo6Es9CZqBjjgi7Py7lyFrL+nkd5E=;
MIME-Version: 1.0
References: <CAJHtznz+vMtytUxnf73L474TcDUqsZpTHLTnhHL4E53CCQdibA@mail.gmail.com> <CAF+90c-5CeZfyo2zBeoM63NDK-j2h6WTjvdT-yiKy040wVUm-w@mail.gmail.com>
In-Reply-To: <CAF+90c-5CeZfyo2zBeoM63NDK-j2h6WTjvdT-yiKy040wVUm-w@mail.gmail.com>
Date: Fri, 9 Aug 2019 00:25:05 +0300
Message-ID: <CAJHtznzFSP4u7HggZPmyi27ejUie6x+kUytvTCd+WTpsKwFwag@mail.gmail.com>
To: Nikita Popov <nikita.ppv@gmail.com>
Cc: Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000009d6778058fa1b11b"
Subject: Re: [PHP-DEV] Bringing Peace to the Galaxy
From: zeev@php.net (Zeev Suraski)

--0000000000009d6778058fa1b11b
Content-Type: text/plain; charset="UTF-8"

On Fri, Aug 9, 2019 at 12:02 AM Nikita Popov <nikita.ppv@gmail.com> wrote:

> This is basically what I have been advocating for a while now already,
> somewhat hidden between all the other noise of the "namespace-scoped
> declares" thread. The model I would like to follow are Rust editions (
> https://doc.rust-lang.org/edition-guide/editions/index.html). In PHP
> right now, the way to do this technically would be based on a
> declare(edition=2020) in every file. I was hoping to make this a
> per-package declaration instead, but haven't found the perfect way to do
> this right now.
>

I think it's similar, but not quite the same, at least as far as what I
understood from what you were saying on that thread (I just reread it).
First, I think it's important we don't only focus on what we're going to
change - but also on what we're going to keep.  The motivation should not
be slow eventual migration from one codebase to another.  We would have
two, long-term supported codebases - a lot closer to C and C++ than to
different editions of a single language.  The distance between them would
be quite substantial from the get-go - and will likely grow farther as time
goes by, similarly to the situation with C and C++.

Also - I think that we should do our very best to get this "P++" right the
first time, as opposed to iterate on it and release editions that provide a
steady stream of change and breakage.  Of course - we can add new features
and evolve existing ones - but this should be a lot more similar to the
mini versions / feature releases we currently have.

It's certainly similar in concept, but not quite the same.

Zeev

--0000000000009d6778058fa1b11b--