Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:41905
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 85.214.94.56 as permitted sender)
Date: Thu, 13 Nov 2008 20:01:11 +0100
Reply-To: Marcus Boerger <helly@php.net>
Message-ID: <1317982846.20081113200111@marcus-boerger.de>
To: Sebastian Bergmann <sb@sebastian-bergmann.de>
CC: internals@lists.php.net
In-Reply-To: <491B2E81.3070601@sebastian-bergmann.de>
References: <491B2E81.3070601@sebastian-bergmann.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-15
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] ReflectionProperty::setValue() and ReflectionProperty::setAccessible()
From: helly@php.net (Marcus Boerger)

Hello Sebastian,

  allowing to read is more than enough. And ofr the record I did not like
  that at all. If you need to write to a private variable, then obviously
  your class design is wrong. And testing is no argument, as you can nicely
  design so that this is not necessary.

marcus

Wednesday, November 12, 2008, 8:29:05 PM, you wrote:

>  Currently ReflectionProperty::setValue() ignores the setting made by
>  ReflectionProperty::setAccessible(). Is this intentional or was it just
>  forgotten to handle ref->ignore_visibility in setValue()?

>  For some code I am working on it would be really helpful if setValue()
>  could optionally work with private and protected attributes.

> -- 
> Sebastian Bergmann                          http://sebastian-bergmann.de/
> GnuPG Key: 0xB85B5D69 / 27A7 2B14 09E4 98CD 6277 0E5B 6867 C514 B85B 5D69




Best regards,
 Marcus