Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:85783 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 62624 invoked from network); 13 Apr 2015 16:02:37 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 13 Apr 2015 16:02:37 -0000 Authentication-Results: pb1.pair.com smtp.mail=francois@php.net; spf=unknown; sender-id=unknown Authentication-Results: pb1.pair.com header.from=francois@php.net; sender-id=unknown Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 212.27.42.2 as permitted sender) X-PHP-List-Original-Sender: francois@php.net X-Host-Fingerprint: 212.27.42.2 smtp2-g21.free.fr Received: from [212.27.42.2] ([212.27.42.2:37273] helo=smtp2-g21.free.fr) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 90/D2-41712-B98EB255 for ; Mon, 13 Apr 2015 12:02:35 -0400 Received: from moorea (unknown [82.240.16.115]) by smtp2-g21.free.fr (Postfix) with ESMTP id DAB2F4B0150; Mon, 13 Apr 2015 18:00:02 +0200 (CEST) Reply-To: To: "'Johannes Ott'" , References: In-Reply-To: Date: Mon, 13 Apr 2015 18:02:21 +0200 Message-ID: <006d01d07603$3a104a70$ae30df50$@php.net> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQGcPDOFlN64TDw9rZa5hwpPQ7e8Cp2zhlBQ Content-Language: fr X-Antivirus: avast! (VPS 150413-0, 13/04/2015), Outbound message X-Antivirus-Status: Clean Subject: RE: [PHP-DEV] New RFC draft "static class constructor" From: francois@php.net (=?utf-8?Q?Fran=C3=A7ois_Laupretre?=) > De : Johannes Ott [mailto:mail@deroetzi.de] > finally I managed to do my first RFC draft. >=20 > https://wiki.php.net/rfc/static_class_constructor >=20 > I hope I have done everything correct so far and I'm looking forward = to > your feedback on it. Interesting. It also allows to respect PSR-1, which says 'Files SHOULD = either declare symbols (classes, functions, constants, etc.) or cause = side-effects (e.g. generate output, change .ini settings, etc.) but = SHOULD NOT do both' (see = https://github.com/flaupretre/automap/blob/develop/src/classes/Automap.ph= p for an example). Comments : - __static is ambiguous and does not reflect the method's role. Even if = longer, I definitely prefer __staticInit or, even better, __classInit. - IMO, the method should be called when the class is created, just after = every parent class and implemented interfaces are created. If some load = a bunch of classes they don't use, that's their problem, not ours. It is = not a reason to follow a two-step process. A properly written program = uses autoloading and loads the classes it needs only. Another argument = is that I'm not sure it is possible to catch every case of read access = to static properties. - I think you should provide a destructor method because there can be a = need to cleanup/close the resources opened when initializing the class. = It can be open files, sockets, or any other resource, but, IMO, they = need to be explicitly closed when the request ends. Regards Fran=C3=A7ois