Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:22991
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Date: Thu, 27 Apr 2006 15:19:48 +0200
Reply-To: Marcus Boerger <helly@php.net>
Message-ID: <1421874376.20060427151948@marcus-boerger.de>
To: Edin Kadribasic <edink@emini.dk>
Cc: php internals <internals@lists.php.net>
In-Reply-To: <444FDF4C.4020303@emini.dk>
References: <444E0854.2000804@emini.dk> <200604251602.42837.bu@orbitel.bg> <444E2108.8050203@iamjochem.com> <749874265.20060426211537@marcus-boerger.de> <444FDF4C.4020303@emini.dk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Static properties
From: helly@php.net (Marcus Boerger)

Hello Edin,

Wednesday, April 26, 2006, 10:59:56 PM, you wrote:

> Marcus Boerger wrote:
>> It is just some decision that was taken that the newer OO stuff should be a
>> bit more strict.

> I don't remember any such decision. I don't even remember a discussion 
> about it. I'm aware of the efforts of some people to make PHP less PHP 
> and more Java and thus we end up in a situation where:

There was no endless discussion like we to often do on the list but instead
it was just something we came to agree upon among those implementing it
while implementing it.

> class foo{}; foo::$bar = 1;

To cut the story short, any feature might have an advantage for somebody but
also a heavy disadvantage for somebody else. But in the end if we'd agree to
add this feature we#d also end up in supporting interception of static
properties which we probably do not want.

Best regards,
 Marcus