That can be handled with read_property and write_property handlers. Disallowing access to PHP users is an artificial restriction that we should find ways around.
If you have these handlers, why you need read-made persistent zvals? You can construct any zval you want once property is read and you can do anything you want once property is written, what persistent zval would give you then?
-- Stanislav Malyshev, Zend Products Engineer [EMAIL PROTECTED] http://www.zend.com/
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
