Re: (s|g)etStaticPropertyValue

I think for me, it is the most comfortable way to refelect the properties. When it is refelecting it should follow a std. pattern ----- Original Message ----- From: "Timm Friebe" <thekid@thekid.de> To: "internals" <internals@lists.php.net> Sent: Sunday, March 06, 2005 5:11 PM Subject: [PHP-DEV] (s|g)etStaticPropertyValue > 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 > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > >