Hi,
I'd like to suggest a change to how the read_property object handler operates.
Wouldn't it be reasonable for the engine to use get_property_ptr_ptr() whenever
it wants to modify a property and get rid of using read_property() for write
access?
That would make rather simple ops like concatenation, in-/decrementation etc
work again with overloaded internal classes. Just make the engine use
read_property() followed by a write_property() when there's no
get_property_ptr_ptr().
Punish me if I'm really that far off.
Thoughts?
Michael
Hello,
Does that fix the problem where:
$object->theArray[] = (...);
is invalid when 'theArray' is implemented using __get()?
Whoever fixes that one could get all free drinks at PHP conferences:
PHP Hacker: "Hi, I'm the guy who made it so you can add items to an array which
is returned through __get()"
PHP Fanboy: "Dude that is so awesome, how could I ever repay you!? Can I buy
you a beer?"
regards,
Peter
--- Michael Wallner mike@php.net wrote:
Hi,
I'd like to suggest a change to how the read_property object handler
operates.Wouldn't it be reasonable for the engine to use get_property_ptr_ptr()
whenever
it wants to modify a property and get rid of using read_property() for write
access?That would make rather simple ops like concatenation, in-/decrementation etc
work again with overloaded internal classes. Just make the engine use
read_property() followed by a write_property() when there's no
get_property_ptr_ptr().Punish me if I'm really that far off.
Thoughts?
Michael
--
Send instant messages to your online friends http://au.messenger.yahoo.com
Peter Hodge wrote:
Hello,
Does that fix the problem where:
$object->theArray[] = (...);
is invalid when 'theArray' is implemented using __get()?
No. It's about internal classes and information stored in C structures.
Regards,
Michael