Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:50749
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain basnetworks.net from 208.97.132.145 cause and error)
DomainKey-Status: good
DomainKey-Signature: a=rsa-sha1; c=nofws; d=basnetworks.net; h=message-id
	:in-reply-to:references:date:subject:from:to:cc:mime-version
	:content-type:content-transfer-encoding; q=dns; s=
	basnetworks.net; b=0vZbgg8iurHL5jJIgM1n36pDlr6ihacGMhPooeIcLMAIJ
	MeZx6Upd53qlZstkhCODjS8LQeRQfWaNySUW3oqWKODXB22HNi+ipp56dbfEPdcm
	6BW14UdTTyts5bXaiaRj/U8aWrSU2Ksq2/SbTmQyu0ZUkUoWsGLM8KlsowYDr0=
Message-ID: <1faa4c3db62771335db714507ac2adfa.squirrel@webmail.basnetworks.net>
In-Reply-To: <4CF5118B.2030300@sugarcrm.com>
References:
    <ae7aa0536c47a2ac725222d49918183f.squirrel@webmail.basnetworks.net>
    <003601cb8fd0$f6494e80$e2dbeb80$@com> <4CF3B855.5010406@sugarcrm.com>
    <003401cb8fee$1be39840$53aac8c0$@com>
    <2450924ae03481f5b1382a7f00e5743d.squirrel@webmail.basnetworks.net>
    <4CF50245.5020807@sugarcrm.com>
    <ed0a2b6089e32bc3def3c14a1f510246.squirrel@webmail.basnetworks.net>
    <4CF5118B.2030300@sugarcrm.com>
Date: Tue, 30 Nov 2010 19:31:22 -0500
To: "Stas Malyshev" <smalyshev@sugarcrm.com>
Cc: "president@basnetworks.net" <president@basnetworks.net>,
 "internals@lists.php.net" <internals@lists.php.net>
User-Agent: SquirrelMail/1.4.21
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] RFC: C-sharp style property get/set syntax for PHP
From: president@basnetworks.net

>> That is true for PHP variables.  isset is basically saying "does this
>> variable exist", and unset is saying to get rid of it.
>
> This is also true for object properties - see magic methods. I don't se=
e
> why you shouldn't be able to unset them - you can do that with regular
> properties... So what you imagine would happen if you call
> unset($foo->property) or isset($foo->property)?

As I replied elsewhere:

Its not a matter of consistency - Properties, as a cross-language concept
are not meant to work that way.  You need to think of a property as a set
of two methods that just have a pretty syntax.  Methods cannot be unset,
and nor should properties be allowed to.  isset() should simply tell us
whether a property with the specified name is part of the class or not.

isset() in the way you suggest would just be confusing.  It would allow i=
s
to say that a property does not exist, when in fact it does exist.  This
is not logical.

__isset is a whole different matter, without it we would have to assume
that every possible member name in a class either exists or does not
exist.  This is because __isset, __get, __set and __unset can handle ANY
member name.

Properties are bound to a single member name, therefore, they always
exist, unless you were to physically remove that property from the class,
which, like methods, that is not possible.

- Dennis