Hi Marcus, May be it make sence, but I am not sure with you.
At first, if you think __call()/__get()/__set() mast conform to uniform prototypes and extension will define methods with another prototypes then PHP should not work with such extensions. Warning is very bed decision for binary extensions. What will poor PHP programmer think about this warning? Really, it is not a problem for me to add a new function to ext/soap, that will make complicated call with SOAP headers and so on. But changing extension API can be a problem for its users. Thanks. Dmitry. > -----Original Message----- > From: Marcus Boerger [mailto:[EMAIL PROTECTED] > Sent: Thursday, September 09, 2004 21:04 > To: Dmitry Stogov > Cc: [EMAIL PROTECTED] > Subject: Re: [PHP-DEV] SOAP's __call > > > Hello Dmitry, > > Thursday, September 9, 2004, 5:59:11 PM, you wrote: > > > Hi Marcus, > > > Can you explain for what reason you changed prototype of the > > SoapClient::__call? This broke receiving of SOAP headers. > > __call() is an engine feature that requires either three (PHP > 4) or exactly 2 (PHP 5) parameters. If you need a more > complex function then you need to provide a separate function > and probably map both the new and _call onto a combined > implementation. > > best regards > marcus > > -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
