Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:37644
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain googlemail.com designates 209.85.128.186 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=googlemail.com; s=gamma;
        h=message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=VOmD1DOVILkiIrI2XCiSGdvshCcxnwZYSJL0Lx/7PBXjqsA0tFzLd6eNsUaVmW21rsGaTz7qgYqfzvpOriQw021TkXYWZ0NbkiDiTWx4mE5GL79vCeWo2FXGI+ZgkSXngFLuZ+5bni/WlGFVqj4Sjnp2q/0kF5URVam9wMqiKtY=
Message-ID: <10845a340805140348j15fa108dv6d616865779128c5@mail.gmail.com>
Date: Wed, 14 May 2008 11:48:13 +0100
Reply-To: RQuadling@GoogleMail.com
To: "Christian Schneider" <cschneid@cschneid.com>
Cc: "Marcus Boerger" <helly@php.net>, "Stanislav Malyshev" <stas@zend.com>, 
	internals@lists.php.net
In-Reply-To: <76FF1B4A-1CAB-407A-9E6D-41E8C1137FCB@cschneid.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <48169695.9040803@omegavortex.net>
	 <489751132.20080506214551@marcus-boerger.de>
	 <CC6F77E6-FA3C-4CE9-A82D-D3686A4AA4BD@procata.com>
	 <10845a340805070633q2316a598lc1a69f259c523341@mail.gmail.com>
	 <92634160.20080512164700@marcus-boerger.de>
	 <10845a340805120803k2587870bnf890ce44765f5e97@mail.gmail.com>
	 <721653902.20080513155302@marcus-boerger.de>
	 <4829A0C9.5050308@cschneid.com>
	 <1629174644.20080514020633@marcus-boerger.de>
	 <76FF1B4A-1CAB-407A-9E6D-41E8C1137FCB@cschneid.com>
Subject: Re: [PHP-DEV] Class Properties in Interfaces?
From: rquadling@googlemail.com ("Richard Quadling")

2008/5/14 Christian Schneider <cschneid@cschneid.com>:
>
> Am 14.05.2008 um 02:06 schrieb Marcus Boerger:
>>>
>>> So you are saying that
>>>       $o_Foo->bar = array(42);
>>> is ok when the class "expects" a string but
>>>       unset($o_Foo->bar);
>>> or (as as slight variation)
>>>       $o->Foo->bar = null;
>>> is not?
>>
>> I Do not get the connection here? And since when can we 'expect' a string
>> only for a property?
>
> You stated that allowing unset() is a bug. I replied that unset() is not
> different from setting the value to array(42) or null and should be allowed.
>
> Apropos 'expect': A programmer of a class can have some expectations of what
> is stored in attributes, PHP does not enforce these expectations (hence I
> put expect in quotes). And just to make it clear: I want to keep it that
> way, I do not want PHP to become more strict than it is.
>
> So I completely agree with Stas here.
>
> - Chris

Chris (and others).

_IF_ the property was defined in an interface, should "unset" be
"allowed" to remove the property?

The current behaviour of allowing a property of a normal class to be
removed is debatable. (It is currently doing so, so for BC it should
probably stay as such).

With the interface though, we _are_ saying we want to enforce its
existence, so it must always exist and as such unset() would/should
have no meaning and be an error (attempting to change an enforced
interface structure).

Maybe this is a difference for E_STRICT?

Richard.


-- 
-----
Richard Quadling
Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731
"Standing on the shoulders of some very clever giants!"