(s|g)etStaticPropertyValue

From: Date: Sun, 06 Mar 2005 11:26:02 +0000
Subject: (s|g)etStaticPropertyValue
Groups: php.internals 
Request: Send a blank email to internals+get-15281@lists.php.net to get a copy of this message
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

« previous php.internals (#15281) next »