Jasper Bryant-Greene wrote:
SLaVKa wrote:
Hey guys just a general question... if you have a
parent::__constructor() call in your constructor function, should that
call ideally be placed before or after the code inside the current
constructor? or it doesnt really matter
That depends on whic
SLaVKa wrote:
Hey guys just a general question... if you have a
parent::__constructor() call in your constructor function, should that
call ideally be placed before or after the code inside the current
constructor? or it doesnt really matter
That depends on which code you want to run first. S
Try 'parent::'
On Wed, 7 Feb 2001, Aaron Tuller wrote:
> At 12:13 PM +0100 2/7/01, Christian Reiniger wrote:
> >On Wednesday 07 February 2001 05:14, Aaron Tuller wrote:
> > > $parentClass = get_parent_class($this);
> >> eval("$parentClass::$parentClass();");
> >>
> >> still, I think I should
At 12:13 PM +0100 2/7/01, Christian Reiniger wrote:
>On Wednesday 07 February 2001 05:14, Aaron Tuller wrote:
> > $parentClass = get_parent_class($this);
>> eval("$parentClass::$parentClass();");
>>
>> still, I think I should be able to do what I wrote below.
>
>Um, you know the name of your pa
On Wednesday 07 February 2001 05:14, Aaron Tuller wrote:
> ok, I == dumb. this works:
>
> $parentClass = get_parent_class($this);
> eval("$parentClass::$parentClass();");
>
> still, I think I should be able to do what I wrote below.
Um, you know the name of your parent class, so why do you use
ok, I == dumb. this works:
$parentClass = get_parent_class($this);
eval("$parentClass::$parentClass();");
still, I think I should be able to do what I wrote below.
-aaron
At 8:05 PM -0800 2/6/01, Aaron Tuller wrote:
>why doesn't this work?
>
>$parentClass = get_parent_class($this);
>parent::{
6 matches
Mail list logo