Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:89133
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain adamharvey.name designates 209.85.217.178 as permitted sender)
MIME-Version: 1.0
Sender: adam@adamharvey.name
In-Reply-To: <alpine.DEB.2.20.1511091643530.14376@whisky.home.derickrethans.nl>
References: <CANUQDCh5R3dir=fzb3uGgKUrbk266BR6xWLn4Gt0-OWCOfZtAQ@mail.gmail.com>
 <alpine.DEB.2.20.1511091643530.14376@whisky.home.derickrethans.nl>
Date: Mon, 9 Nov 2015 15:51:47 -0800
Message-ID: <CADajX4BUs563WrSRtu4JXUpcoQzXXRPhsT8Ucbids-EPzbC1fQ@mail.gmail.com>
To: Derick Rethans <derick@php.net>
Cc: Niklas Keller <me@kelunik.com>, PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] Null bytes in anonymous class names
From: aharvey@php.net (Adam Harvey)

On 9 November 2015 at 13:46, Derick Rethans <derick@php.net> wrote:
> On Thu, 5 Nov 2015, Niklas Keller wrote:
>
>> I discovered today that anonymous class names contain a null byte
>> right after "class@anonymous". I don't think class names should
>> contain non-printable characters.
>>
>> How about removing that null byte?
>
> I would suggest replacing it with something else. As I am making this
> work for Xdebug, I really need to ship the full name to the IDE so that
> they can later do look-ups on anonymous class properties, and with the
> \0 the IDEs seem to fuck this up. I suggest using another @ instead of
> the \0.

Just to add another voice: +1 for this (or something similar). Having
the \0 can be worked around, but just not having to deal with it at
all is a hell of a lot easier for those of us working on third party
tooling.

Adam