Re: New feature: sequential constructors
| From: | Ralf Lang | Date: | Wed, 03 Jul 2013 18:12:17 +0000 |
| Subject: | Re: New feature: sequential constructors | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-68052@lists.php.net to get a copy of this message | ||
On 03.07.2013 20:05, Sanford Whiteman wrote:
> a new keyword is problematic, perhaps this same
>> behaviour could be enacted in cases where an inheriting class has a
>> constructor and the base class' constructor is defined as final i.e. rather
>> than causing an error, the final constructor is executed first, followed by
Most often if I need a super __construct(), I don't need it exactly
before or exactly after the bottom constructor but at a specific point
where I can setup super's input data and do stuff to its output.
What is the typical use case for calling all supers (before or after the
class' __construct itself) ?
--
Ralf Lang
Linux Consultant / Developer
Tel.: +49-170-6381563
Mail: lang@b1-systems.de
B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
Attachment: [application/pgp-signature] OpenPGP digital signature signature.asc
Attachment: [application/pgp-signature] OpenPGP digital signature signature.asc