On 25.03.2010, at 21:13, Stefan Marr wrote: > On 24 Mar 2010, at 11:50, Lukas Kahwe Smith wrote: >> "In case of the above definition of Talker, PHP will show a warning that >> there have been conflicts and name the methods smallTalk() and bigTalk() as >> the reason of this conflict. Therefore, neither of the given implementations >> will be available in the class." >> >> I think this is a fundamental decision, should it be a warning or a fatal >> error? Generally I prefer PHP to keep on going whenever it can. I guess in >> most cases if we stick to a warning the user will end up with a fatal error >> anyway, but it might not be so clear why the given method is unavailable. >> But there should still be a warning, which I guess cannot be suppressed all >> that easily. > Well, I do not like a fatal errors. This problem does not leave the engine in > an undefined state, and personally, I think, fatals should only be caused by > something which really cannot be handled. > > Since we have __call, there might even be something executable.
Yeah, I agree, just wanted to bring this point up. I am right that this warning cannot be suppressed via some @ magic and so if at all would need to be suppressed by a custom error handler? regards, Lukas Kahwe Smith m...@pooteeweet.org -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
