Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:15282 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 40215 invoked by uid 1010); 6 Mar 2005 11:51:05 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 40191 invoked from network); 6 Mar 2005 11:51:05 -0000 Received: from unknown (HELO hotmail.com) (127.0.0.1) by localhost with SMTP; 6 Mar 2005 11:51:05 -0000 X-Host-Fingerprint: 202.174.149.6 unknown Linux 2.4/2.6 Received: from ([202.174.149.6:34518] helo=bhakari.websurfer.com.np) by pb1.pair.com (ecelerity HEAD r(5124)) with SMTP id 15/44-29225-5AEEA224 for ; Sun, 06 Mar 2005 06:51:05 -0500 Received: (qmail 2190 invoked by uid 107); 6 Mar 2005 11:50:51 -0000 Received: from unknown (HELO server) (202.174.149.241) by bhakari.websurfer.com.np with SMTP; 6 Mar 2005 11:50:51 -0000 Message-ID: <008e01c52242$be732410$0100a8c0@server> To: "Timm Friebe" , "internals" References: <1110108362.335.19.camel@localhost> Date: Sun, 6 Mar 2005 17:35:46 +0545 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.3790.181 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.181 Subject: Re: [PHP-DEV] (s|g)etStaticPropertyValue From: npguy@websurfer.com.np ("sarose") 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" To: "internals" 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 > >