Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:50732 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 62719 invoked from network); 30 Nov 2010 14:58:40 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 30 Nov 2010 14:58:40 -0000 Authentication-Results: pb1.pair.com header.from=johannes@schlueters.de; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=johannes@schlueters.de; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain schlueters.de from 217.114.211.66 cause and error) X-PHP-List-Original-Sender: johannes@schlueters.de X-Host-Fingerprint: 217.114.211.66 unknown Solaris 10 (beta) Received: from [217.114.211.66] ([217.114.211.66:60821] helo=config.schlueters.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 33/84-35426-99B05FC4 for ; Tue, 30 Nov 2010 09:35:06 -0500 Received: from [192.168.1.31] (ppp-93-104-37-132.dynamic.mnet-online.de [93.104.37.132]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by config.schlueters.de (Postfix) with ESMTPSA id 054594B491; Tue, 30 Nov 2010 15:35:01 +0100 (CET) To: president@basnetworks.net Cc: Stas Malyshev , internals@lists.php.net In-Reply-To: References: <003601cb8fd0$f6494e80$e2dbeb80$@com> <4CF3B855.5010406@sugarcrm.com> <003401cb8fee$1be39840$53aac8c0$@com> <2450924ae03481f5b1382a7f00e5743d.squirrel@webmail.basnetworks.net> <4CF50245.5020807@sugarcrm.com> Content-Type: text/plain; charset="UTF-8" Date: Tue, 30 Nov 2010 15:34:54 +0100 Message-ID: <1291127695.6129.16.camel@guybrush> Mime-Version: 1.0 X-Mailer: Evolution 2.30.2 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] RFC: C-sharp style property get/set syntax for PHP From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=) On Tue, 2010-11-30 at 09:15 -0500, president@basnetworks.net wrote: > That is true for PHP variables. isset is basically saying "does this > variable exist", and unset is saying to get rid of it. > > Because properties (as defined in my RFC) are not a variable, but rather a > set of methods, I do not think there would be any way to "unset" them. > Like a method, once they are defined, you cannot get rid of them. > Therefore "overloading" isset and unset would not make any sense here. This is different from the PHP Language then. You can isset() and unset() "native" properties. And use __isset() and __unset() magic methods. A new feature should be consistent with the language definition. johannes