Re: Failed 21/178 test scripts, 88.20% okay. 109/1044 subtests failed, 89.56% okay

2004-06-10 Thread Stas Bekman
Earl Ruby wrote: -8<-- Start Bug Report 8<-- 1. Problem Description: At the end of "make test" I got the following messages. (When 10 out of 5 tests fail... you know it's bad!) Failed Test Stat Wstat Total Fail Failed List of Failed

Bankrott des Gesundheitswesens durch Auslaender! <8314>

2004-06-10 Thread jand
Die verschwiegenen Gruende der Kostenexplosion: Unlaengst aeusserte der Vorsitzende des Bayerischen Hausaerzteverbandes, Dr. Wolfgang Hoppenthaller, dass eine grosse Zahl auslaendischer 'Gesundheitstouristen' mit den Chipkarten ihrer Angehoerigen und Freunde bei uns die aerztliche Versorgung in

Re: [mp2] one more pass on mp2/apr read() functions

2004-06-10 Thread Joe Schaefer
Stas Bekman <[EMAIL PROTECTED]> writes: > Joe Schaefer wrote: [...] > > perl's eval {} is very slow, and doesn't easily > > How slow? All mod_perl handlers run as eval {} I retract that, sorry. eval BLOCK isn't bad, it's eval STRING that I was thinking of. -- Joe Schaefer

Failed 21/178 test scripts, 88.20% okay. 109/1044 subtests failed, 89.56% okay

2004-06-10 Thread Earl Ruby
-8<-- Start Bug Report 8<-- 1. Problem Description: At the end of "make test" I got the following messages. (When 10 out of 5 tests fail... you know it's bad!) Failed Test Stat Wstat Total Fail Failed List of Failed ---

Re: [mp2] one more pass on mp2/apr read() functions

2004-06-10 Thread Stas Bekman
Joe Schaefer wrote: Stas Bekman <[EMAIL PROTECTED]> writes: Joe Schaefer wrote: [...] perl's eval {} is very slow, and doesn't easily How slow? All mod_perl handlers run as eval {} I retract that, sorry. eval BLOCK isn't bad, it's eval STRING that I was thinking of. Ah :) You scared me for a

Re: cvs commit: modperl-2.0/t/protocol/TestProtocol echo_block.pm echo_timeout.pm

2004-06-10 Thread Stas Bekman
Geoffrey Young wrote: Stas Bekman wrote: Geoffrey Young wrote: e.g.: % cvs co -D 20040601 -d mp2-20040601 modperl-2.0 yeah, I can try when I get the time (heh). but it might not be mod_perl's fault so I'll really need to do an httpd regression as well. OK. Either way it's better to get the bugs

Re: cvs commit: modperl-2.0/t/protocol/TestProtocol echo_block.pm echo_timeout.pm

2004-06-10 Thread Geoffrey Young
Stas Bekman wrote: > Geoffrey Young wrote: > >>> e.g.: >>> % cvs co -D 20040601 -d mp2-20040601 modperl-2.0 >> >> >> >> yeah, I can try when I get the time (heh). but it might not be mod_perl's >> fault so I'll really need to do an httpd regression as well. > > > OK. Either way it's better to

Re: APR::Error constant matching

2004-06-10 Thread Stas Bekman
[adjusting the subject] Joe Schaefer wrote: Stas Bekman <[EMAIL PROTECTED]> writes: [...] I'm also going to add a wrapper to replace the crafty if (ref $@ eq 'Apache::Error' && $@ == APR::TIMEUP) { ... } with: if (APR::Error::foo($@, APR::TIMEUP)) { ... } OTOH, why not just write if ($@ == APR:

Re: [mp2] one more pass on mp2/apr read() functions

2004-06-10 Thread Stas Bekman
Joe Schaefer wrote: Stas Bekman <[EMAIL PROTECTED]> writes: [...] but somehow I'd rather be attaching handlers to exception classes (like Java & C# do), not dispatching on the value of $@ directly. Example? perl's eval {} is very slow, and doesn't easily How slow? All mod_perl handlers run as eva