Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:50706
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain schlueters.de from 217.114.211.66 cause and error)
To: larry@garfieldtech.com
Cc: internals@lists.php.net
In-Reply-To: <4CF40195.7060101@garfieldtech.com>
References:
	 <ae7aa0536c47a2ac725222d49918183f.squirrel@webmail.basnetworks.net>
	 <AANLkTi=wY_djZ=4ZKW7sV4zKpr_X_uEo3iqkA+pSDCsy@mail.gmail.com>
	 <4CF3B903.6000204@gmail.com>  <4CF3EE8A.4000405@garfieldtech.com>
	 <1291056116.6129.1.camel@guybrush>  <4CF40195.7060101@garfieldtech.com>
Content-Type: text/plain; charset="UTF-8"
Date: Mon, 29 Nov 2010 20:56:57 +0100
Message-ID: <1291060617.6129.13.camel@guybrush>
Mime-Version: 1.0
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 Mon, 2010-11-29 at 13:40 -0600, larry@garfieldtech.com wrote:
> I still want to keep the performance implications in mind, as this 
> sounds like something that we'd want to use a lot but could also cost a 
> lot more than it seems at first glance if we're not careful.

By making properties in memory a little bigger one might write the
accessors in the same table as the actual properties one might possibly
reduce the CPU requirement abit. While one has to touch most places
dealing with properties internally (while that's probably needed
anyways). But well, unless there is an implementation all performance
ideas are guesses ... educated guesses at best.

johannes