Re: SOAP's __call
| From: | Marcus Boerger | Date: | Fri, 10 Sep 2004 21:39:11 +0000 |
| Subject: | Re: SOAP's __call | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-12724@lists.php.net to get a copy of this message | ||
Hello Dmitry,
Thursday, September 9, 2004, 7:39:03 PM, you wrote:
> 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.
Na, i have to thank that you did the work and renamed that function.
The point is that we need to prevent ourselvs from misusing some
facilities because we would write bad/inconsistent or even faulting
code.
best regards
marcus