Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:15281
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
To: internals <internals@lists.php.net>
Content-Type: text/plain
Date: Sun, 06 Mar 2005 12:26:02 +0100
Message-ID: <1110108362.335.19.camel@localhost>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: (s|g)etStaticPropertyValue
From: thekid@thekid.de (Timm Friebe)

Hello,
I saw there are two new ReflectionClass methods:

  * getStaticPropertyValue()
  * getStaticPropertyValue()

How do these differ (excepting being one method call) from:

  $value= $reflectionClass->getProperty('instance')->getValue();

and

  $reflectionClass->getProperty('instance')->setValue($value);

?

Instead of adding all kinds of feature bloat to the Reflection API,
couldn't this be left to people who extend it?

And if we must have these methods because of performance reasons, why
restrict them to static properties? Just because I can write
$instance->{$variable} and not Classname::$variable?

-- 
Timm
If it ain't broken, it doesn't have enough features yet