On Sat, 25 Dec 2004, Jacques Marneweck wrote:
> SMTP on lists.php.net is down and when I commit files to CVS I'm
> getting the following:
>
> 63981 LOGINFO [EMAIL PROTECTED] jacques phpweb usage.php,1.64,1.65
> 63982 Mailing the commit email to [EMAIL PROTECTED]
> connect 216.92.131.4:25 failed at
Did you look into my latest patch and try with it?
WF>>I've been working with Edin to try and track down what caused the
WF>>sudden round of crashes in the COM extension in the latest 4.3
WF>>release, and it seems that the PZVAL_UNLOCK that Stas introduced in
WF>>this commit:
WF>>
WF>>http://viewc
This doesn't really clear it out.
I can either use the "cleaner" method, and an exception would be
raised when I'd try to call NULL(), or, have the OPTION to check
whether it's NULL before calling it. IMHO It's much more consistent
and clean.
You STILL can use exceptions the way you did, and in AD
[EMAIL PROTECTED] wrote:
> Why not just returning null when a method does not exist?
> Actually CALLING a non-existing method should be treated as an error...
Because
try {
$class = new ReflectionClass($this);
$method = $class->getMethod($this->name);
}
catch (Reflection
Christian Schneider wrote:
>> Calling getMethod() for a method that does not exist is an error and
>> should be consistently treated as such by raising an exception.
>
> I disagree. The same could be said for getenv().
The Reflection API was introduced at the same time as exceptions. It
therefo
