Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:101322
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain dqxtech.net from 209.85.215.42 cause and error)
MIME-Version: 1.0
In-Reply-To: <CADyq6sJCiL8+LgsP3S4pLDa+4Cuv4iBMrAR4ZGE-yTu7D66rbg@mail.gmail.com>
References: <CAH0Uv3Hf_uTgHo5bg5x_A5DUfkB7bjSXzPZ5yXGS3JDdDJWW+A@mail.gmail.com>
 <CADyq6sKLc=7tUt_bffXsmvvc2nBBp4mHiwzR_F=O3y85vUJCdA@mail.gmail.com>
 <CAH0Uv3ECNFAUN_mjaG3dacwoK617HzLmFJOnwxJSN5SP8POyVQ@mail.gmail.com> <CADyq6sJCiL8+LgsP3S4pLDa+4Cuv4iBMrAR4ZGE-yTu7D66rbg@mail.gmail.com>
Date: Mon, 11 Dec 2017 11:24:02 +0100
Message-ID: <CAH0Uv3Gv9-tvwHPheogLDOAgx6Gr+YZk5pCLDkny7q-U8o4ePA@mail.gmail.com>
To: Marco Pivetta <ocramius@gmail.com>
Cc: PHP Internals List <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] Reflection API: Add ::getFullName() method.
From: andreas@dqxtech.net (Andreas Hennings)

>> >
>> > Obviously, the `\0` is horrible and can probably be improved: depends on
>> > whether the API is intended for human or machine consumption. If it is
>> > machine consumption, strings are the wrong approach anyway.
>>
>> Machine or human?
>> One goal is that these names can be used as array keys or unique
>> identifiers whenever we deal with a collection of reflectors of mixed
>> type.
>> At the same time, the name is designed to be very close to what is
>> printed in exception messages, @see doc comment, etc.
>> In this case, I don't see a conflict between human-readable and
>> machine-readable.
>>
>> Maybe when you say "machine consumption" you are thinking of something
>> else?
>
>
> Machine consumption would be VOs, not strings ;-)

One purpose of such names would be that they can be saved in a file or
database, and read in another process.

If you want a value object, then why not use the reflector object directly?
Ok, because "side effects" - I agree.

If we want a value object, it should be named like "ReflectorHandle",
and then "ClassHandle", "FunctionHandle" etc.
These would provide the name of a class, but not any information about it.

But this should be in a separate method, e.g.
ReflectionClass->getHandle(), and it would be a separate feature for a
separate thread.