Maybe a better solution would be to check if the object implements ArrayAccess and the getArrayCopy method exists in the object's class? If it does not exist then it would behave as it does right now and not encode anything, or we could have it throw an encoding exception.

-Joshua

Dmitry Stogov wrote:
I think you are right.
The patch makes not a lot of sense without support for ArrayAccess.
I would prefer to revert it back (at least in this time).
Joshua?

Thanks. Dmitry.

Hannes Magnusson wrote:
On Dec 27, 2007 2:10 PM, Dmitry Stogov <[EMAIL PROTECTED]> wrote:
dmitry          Thu Dec 27 13:10:20 2007 UTC

  Added files:                 (Branch: PHP_5_3)
    /php-src/ext/soap/tests     server030.phpt server030.wsdl

  Modified files:
    /php-src    NEWS
    /php-src/ext/soap   php_encoding.c
  Log:
Added ability to use SplArrays instead of plain arrays in ext/soap. (Joshua Reese, Dmitry)

You don't think this is going to be confusing for the users in the end?
Slowly adding support for ArrayObject and ArrayIterator (but not
ArrayAccess) to random extensions...
Then within few releases you can use ArrayObject/Iterators here, here
and here - but not there...

Should we maybe start a list of functions/extensions where you can use
"SPL Arrays"?

-Hannes
ps _please_ use the [DOC] tag if you want new features to be
documented by the phpdoc team.



--
PHP CVS Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to