Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:68052 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 71405 invoked from network); 3 Jul 2013 18:12:23 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 3 Jul 2013 18:12:23 -0000 Authentication-Results: pb1.pair.com smtp.mail=lang@b1-systems.de; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=lang@b1-systems.de; sender-id=pass Received-SPF: pass (pb1.pair.com: domain b1-systems.de designates 84.200.69.220 as permitted sender) X-PHP-List-Original-Sender: lang@b1-systems.de X-Host-Fingerprint: 84.200.69.220 mx1.b1-systems.de Received: from [84.200.69.220] ([84.200.69.220:56120] helo=mx1.b1-systems.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id CA/17-30639-58964D15 for ; Wed, 03 Jul 2013 14:12:22 -0400 Received: from [192.168.1.17] (cable-158-181-84-94.cust.telecolumbus.net [158.181.84.94]) by mx1.b1-systems.de (Postfix) with ESMTPSA id EA3264075 for ; Wed, 3 Jul 2013 20:08:04 +0200 (CEST) Message-ID: <51D46981.7050902@b1-systems.de> Date: Wed, 03 Jul 2013 20:12:17 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6 MIME-Version: 1.0 To: internals@lists.php.net References: <1668753851.20130703140514@cypressintegrated.com> In-Reply-To: <1668753851.20130703140514@cypressintegrated.com> X-Enigmail-Version: 1.6a1pre Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="----enig2DGNOFTTCVJRMAUPTLRWV" Subject: Re: [PHP-DEV] New feature: sequential constructors From: lang@b1-systems.de (Ralf Lang) ------enig2DGNOFTTCVJRMAUPTLRWV Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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. r= ather >> than causing an error, the final constructor is executed first, follow= ed 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) ? --=20 Ralf Lang Linux Consultant / Developer Tel.: +49-170-6381563 Mail: lang@b1-systems.de B1 Systems GmbH Osterfeldstra=C3=9Fe 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537 ------enig2DGNOFTTCVJRMAUPTLRWV Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlHUaYEACgkQCs1dsHJ/X7C5iQCgsm4ewxfcKj4CcwAc2Z0I1KHv PmYAn1Cap0UKSAX7sNI63deD6ZmWiImk =KrvM -----END PGP SIGNATURE----- ------enig2DGNOFTTCVJRMAUPTLRWV--