Hi:
On 09 Aug 2011, at 19:10, Joey Smith wrote:
> On Mon, Aug 08, 2011 at 03:52:37PM +0100, Keloran wrote:
>> There seems to be a bug in traits that if you use any of the GLOBAL vars it
>> segfaults
>
>
>
> I'm not sure it's clear from Keloran's code example here, so I thought I'd
> point
> ou
On Mon, Aug 08, 2011 at 03:52:37PM +0100, Keloran wrote:
> There seems to be a bug in traits that if you use any of the GLOBAL vars it
> segfaults
I'm not sure it's clear from Keloran's code example here, so I thought I'd point
out that the problem only seems to happen if you include the trait d
There seems to be a bug in traits that if you use any of the GLOBAL vars it
segfaults
e.g.
getStuff("tester");
}
}
that causes a segfault
change the trait to
wrote:
> On 07/25/2011 02:05 PM, Stefan Marr wrote:
> > Hi Johannes:
> >
> > 2011/7/25 Johannes Schlüter :
> >
> >> Now I use reflecti
On 07/25/2011 02:05 PM, Stefan Marr wrote:
> Hi Johannes:
>
> 2011/7/25 Johannes Schlüter :
>
>> Now I use reflection on this:
>>
>> $rc = new ReflectionClass('C');
>> print_r($rc->getTraitAliases());
>>
>> Array
>> (
>>[tc] => T1::t1
>> )
>
> Great, that is nice.
>
>
>> So far so nice but
Hi Johannes:
2011/7/25 Johannes Schlüter :
> Now I use reflection on this:
>
> $rc = new ReflectionClass('C');
> print_r($rc->getTraitAliases());
>
> Array
> (
> [tc] => T1::t1
> )
Great, that is nice.
> So far so nice but I'm missing the information where C::t1() is coming
> from. In the r
