Re: PerlIOApache_flush() [was $|, flushing, etc... [was Next Release]]

2005-10-30 Thread Stas Bekman
Philip M. Gollucci wrote: Philip M. Gollucci wrote: Stas Bekman wrote: > and if you try my last patch suggestion? Hi, yikes, I'm behind Anyway, I finally got around to trying this. Same result as without. Hopefully, at some point during the week, I'll be able to turn on tracing and the

Re: PerlIOApache_flush() [was $|, flushing, etc... [was Next Release]]

2005-10-30 Thread Philip M. Gollucci
Philip M. Gollucci wrote: Stas Bekman wrote: > and if you try my last patch suggestion? Hi, yikes, I'm behind Anyway, I finally got around to trying this. Same result as without. Hopefully, at some point during the week, I'll be able to turn on tracing and the like and see why nothing cha

Re: PerlIOApache_flush() [was $|, flushing, etc... [was Next Release]]

2005-10-30 Thread Philip M. Gollucci
Stas Bekman wrote: > and if you try my last patch suggestion? Hi, yikes, I'm behind Anyway, I finally got around to trying this. Same result as without. Hopefully, at some point during the week, I'll be able to turn on tracing and the like and see why nothing changed. svn diff Index: src/

Re: make test w/ TEST_FILES

2005-10-30 Thread Stas Bekman
Geoffrey Young wrote: Stas Bekman wrote: Philip M. Gollucci wrote: Stas Bekman wrote: I never use that approach. make test is a way too slow if you need to do repetitive testing. I always do: t/TEST t/apache/content_length_header.t In which case it'll never descend into sub-dirs. A

Re: make test w/ TEST_FILES

2005-10-30 Thread Geoffrey Young
Stas Bekman wrote: > Philip M. Gollucci wrote: > >> Stas Bekman wrote: >> >>> I never use that approach. make test is a way too slow if you need to >>> do repetitive testing. I always do: >>> >>> t/TEST t/apache/content_length_header.t >>> >>> In which case it'll never descend into sub-dirs. >