Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:86346
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.52 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <555E762F.6060704@gmail.com>
References: <CAF+90c8ap8eEt0Bj1jY89AxS58QQ8ExTGGoR-zkRnJgg72UOMQ@mail.gmail.com>
	<555E762F.6060704@gmail.com>
Date: Fri, 22 May 2015 07:30:00 +0700
Message-ID: <CAEZPtU4QOWziHDS=MJiTTc32TBRkK097NY02XnKrv9aFPUnFdw@mail.gmail.com>
To: Stas Malyshev <smalyshev@gmail.com>
Cc: Nikita Popov <nikita.ppv@gmail.com>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a113ac88cb9adf80516a0c25a
Subject: Re: [PHP-DEV] Soft-reserve "void" class name
From: pierre.php@gmail.com (Pierre Joye)

--001a113ac88cb9adf80516a0c25a
Content-Type: text/plain; charset=UTF-8

On May 22, 2015 7:20 AM, "Stanislav Malyshev" <smalyshev@gmail.com> wrote:
>
> Hi!
>
> > I'd like to add "void" to this list, so we have the option to introduce
a
> > void return type in PHP 7.x. I've seen some disagreement as to whether
this
>
> I think this type makes no sense in PHP, but I don't object to having
> note in the docs for people not to name their classes "void" (not that
> there's any reason to do it anyway...). I strongly object to introducing
> any changes in the code though - warnings, etc.

The problem I see with any kind of additional soft reserved words is that
it opens the door to actually reserve them in 7.x. And this is a way more
bigger problem.

If anything, I would rather extend or agree on a BC definitions RFC to
avoid such possible breaks in x.y+1 releases.

Cheers,
Pierre

--001a113ac88cb9adf80516a0c25a--