>> I don't know enough about sockets. is the 0 important? in cases like >> this >> can we return 0E0? > > > 0 is very important, in the particular test in my patch. Using 0E0? But > then we have an inconsistent API, some places we return undef other 0E0? > Granted it is already inconsistent, but the idea is to fix it.
I didn't mean 0E0 instead of undef. I meant 0E0 for 0 - zero but true. that would make only errors return false (undef) while valid values (including zero) would all evaluate to true. I guess I was asking if the numeric '0' was important in such a way that perl's treatment of 0E0 as 0 would not be sufficient, such as when passing the result of one call (0E0) to another APR method that expected the true integer 0. if perl takes care of the translation then this seems like a real solution. >> yes, affecting all interpreters for a given (virtual) server. > > > actually only the current interpreter, you can't affect other > interpreter during request time. if the interpreter scope is per-handler and the new PerlCroakOnFailure is per-directory then you'd have some modules croaking and some not in the same request, right? --Geoff --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
