On 11 December 2017 at 09:23, Andreas Hennings wrote:
>>> These side effects would be that the class loader loads files which can
>>> break things?
>>
>>
>> Yes. Reflecting over a codebase which contains even just polyfills
>> (duplicate classes) can already lead to unexpected crashes. Reflecting
>> These side effects would be that the class loader loads files which can
>> break things?
>
>
> Yes. Reflecting over a codebase which contains even just polyfills
> (duplicate classes) can already lead to unexpected crashes. Reflecting over
> non-PSR-2 code can even lead to worse things such as s
On 11 Dec 2017 09:10, "Andreas Hennings" wrote:
On 11 December 2017 at 09:05, Marco Pivetta wrote:
> On 11 December 2017 at 08:46, Marco Pivetta wrote:
> > Indeed that already exists at
> > https://github.com/Roave/BetterReflection/blob/2.0.1/docs/fe
> atures.md#analysing-types-from-docblock
On 11 December 2017 at 09:05, Marco Pivetta wrote:
> On 11 December 2017 at 08:46, Marco Pivetta wrote:
> > Indeed that already exists at
> > https://github.com/Roave/BetterReflection/blob/2.0.1/docs/
> features.md#analysing-types-from-docblocks
> > - relatively new lib, so it probably didn't ge
On 11 December 2017 at 08:46, Marco Pivetta wrote:
> Indeed that already exists at
> https://github.com/Roave/BetterReflection/blob/2.0.1/
docs/features.md#analysing-types-from-docblocks
> - relatively new lib, so it probably didn't get noticed upfront in here.
Yes, parser / userland solutions e
>
> Documentation tools shouldn't run the code IMO, that means they won't have
> access to that feature.
By "documentation tools" do you mean libraries like phpDocumentor?
You are right, those need to parse anyway, they cannot use reflection API.
But tools for annotation discovery may want to use
Indeed that already exists at
https://github.com/Roave/BetterReflection/blob/2.0.1/docs/features.md#analysing-types-from-docblocks
- relatively new lib, so it probably didn't get noticed upfront in here.
It would probably be a good idea to address the fact that the current
reflection API causes au
Andreas Hennings schrieb am Mo., 11. Dez. 2017, 01:39:
> TLDR:
> I propose to introduce a new class \ReflectionContext (or perhaps
> \ReflectionScope?), to give information about imported aliases and the
> namespace.
>
>
> ## Background / motivation
>
> Some libraries that parse doc comment annot
