Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:7676 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 76011 invoked by uid 1010); 9 Feb 2004 17:49:19 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 75954 invoked from network); 9 Feb 2004 17:49:18 -0000 Received: from unknown (HELO moutng.kundenserver.de) (212.227.126.176) by pb1.pair.com with SMTP; 9 Feb 2004 17:49:18 -0000 Received: from [212.227.126.208] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 1AqFX4-0004S1-00; Mon, 09 Feb 2004 18:49:18 +0100 Received: from [217.80.180.230] (helo=[217.80.180.230]) by mrelayng.kundenserver.de with asmtp (Exim 3.35 #1) id 1AqFX3-0007LQ-00; Mon, 09 Feb 2004 18:49:18 +0100 To: Andrey Hristov Cc: internals@lists.php.net In-Reply-To: <1076347709.4027c33db98cc@hristov.com> References: <1076347709.4027c33db98cc@hristov.com> Content-Type: text/plain Message-ID: <1076348690.535.59.camel@localhost> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.4 Date: Mon, 09 Feb 2004 18:44:50 +0100 Content-Transfer-Encoding: 7bit X-Provags-ID: kundenserver.de abuse@kundenserver.de auth:e958292ea7b1c44e51b2b9ca0a9da460 Subject: Re: [PHP-DEV] Changing the visibility of constructors? From: thekid@thekid.de (Timm Friebe) On Mon, 2004-02-09 at 18:28, Andrey Hristov wrote: > Hello internals, > what's your opinion on whether the constructors must follow one of the > principles of the polymorphism - "The visibility in extending classes must be > the same or better". [...] > Currently this code emits a compilation error. Not just one: Fatal error: Cannot use 'parent' as class name as it is reserved:) AFAIS, you only run into this in cases where your base class has a public constructor or any other public methods extended class might want to make private or protected (see the thread about having a built-in base class with all methods implemented - one more reason for not having one). I'm fine with the current solution. Everything else is sloppy, IMHO. - Timm