Re: Calling parent's constructor

> > This looks sensible. I suggest parent::__parent(), > >though, to go along with __wakeup(), __sleep(), and __delegate(). > > At the risk of giving a few people heart attacks from surprise, I'll agree > with you here. That's the solution I thought about for this issue as well. > Just a thought - If the desired functionality _only_ applies to the parent class constructor why not just __parent(). On the other hand, this could be further extended to call any parent class function with __parent::some_func() and a call to the parent constructor looking like __parent::__parent(). Regards, Alan -- Alan van den Bosch Sanguis Pty Ltd /* All generalisations are false. */