Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:34963
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 64.233.166.181 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=EC6iiz5iOS7o+1/zfbmSFxAkdBwwDT9t3Knms+eGLh1GD7ltKAon2URq42XmG9hGKWzPbR0oORGu+Wf0oYMEeoDcDDLkIVL/ItHlyBotcw9skrDlFXozpTUg0Avr5kNva9M5nl3Fc3bVH4RLXMEnipAPl/vyuhAmEwVTth1qXeQ=
Message-ID: <5a8807d10801280718p6d52f689s3a13c4d8c6521a3f@mail.gmail.com>
Date: Mon, 28 Jan 2008 15:18:50 +0000
Reply-To: robin@soal.org
To: "Marcus Boerger" <helly@php.net>, internals@lists.php.net
In-Reply-To: <1109819085.20080128151237@marcus-boerger.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <5a8807d10801280520u7f8c7a9o8d2ab2efaa9c7644@mail.gmail.com>
	 <1109819085.20080128151237@marcus-boerger.de>
Subject: Re: [PHP-DEV] Protected static props redeclared as public share value across classes
From: rewbs.soal@gmail.com ("Robin Fernandes")

Hi Marcus,

Thanks for the prompt reply and explanation. I have some further
questions though:

> If the base class had the property defined as private
> then the property is private to that specific class and not directly
> accessible by derived classes that is it's name gets prefixed with the class
> name.. So in:
> class A { private static $p; } class B extends A { private static $p; }
> we have two different properties:

Understood. But if we have two separate properties for the reason that
A::$p is not visible to B, then how about these cases?
class A { protected static $p; } class B extends A { protected static $p; }
class A { public static $p; } class B extends A { public static $p; }

In both of those cases, A::$p is visible to the derived class, but the
re-declaration results in A::$p and B::$p being two separate
properties (see pastebin.com/fca2cd5b and pastebin.com/f4f94b32d for a
demonstration). This is one of the reasons I find the case where we
end up with only one property value to be surprising.

Another reason is that, as illustrated in my previous post, PHP's
behaviour doesn't seem to correlate with the inheritance rules of
other languages I'm familiar with: you always end up with two distinct
static properties in Java, C++ and C# (though of course I understand
this fact on its own is does not mean PHP is wrong :).

Lastly, with overridden static methods, PHP always yields two distinct
methods, regardless of the visibility modifiers. See
http://pastebin.com/f27f009c4 . Granted, with methods any other
behaviour would be very odd indeed, but it does emphasize an
inconsistency between method and property inheritance rules in PHP.

So for now I continue to feel this is a little strange. Any further
explanations would be greatly appreciated. :)

Thanks,
Robin

> Best regards,
>  Marcus