> this looks like one of the problems the hacked version of C::Scan (at
> perl.apache.org/~dougm/) fixes.
>
I have the C::Scan from perl.apache.org/~dougm/ . I just rechecked to be
sure. So maybe you have done some more fixes and not uploaded it to
perl.apache.org/~dougm/ ? Also the C::Scan-
Hi Randy,
>That fits with what I find, too - I seem to recall that you
> pointed out earlier a problem with environment variables in mod_perl
> in a different context, specifically "remembering" their old
> values, so this seems to be a general mod_perl problem, at least
> on Win32. It may ev
On Sun, 27 May 2001, barries wrote:
> > there are Apache::Filter::{TIEHANDLE,PRINT} methods, the tie just isn't
> > done automatic for you.
>
> I guess the question is really: why not tie them automatically, given
> that there's not much use for STDIN and STDOUT in the context of a
> filter, it
On Sun, 27 May 2001, barries wrote:
> Since you've done the tieing STDIN/STDOUT bit in the past (1.x), why not
> tie STDIN and STDOUT in modperl_output_filter_handler()? That would make
> filter sub code bit less funky:
>
>sub handler {
>while (<>) {
>print uc ;
>
On Sun, May 27, 2001 at 01:11:25PM -0700, [EMAIL PROTECTED] wrote:
> On Sun, 27 May 2001, barries wrote:
>
> > STDIN/STDOUT would then be restored to their original state (tied or
> > untied) up exit?
>
> there are Apache::Filter::{TIEHANDLE,PRINT} methods, the tie just isn't
> done automatic fo
On Sun, 27 May 2001, Gerald Richter wrote:
> I tried this already. Addtionaly to add the dav_ prefix, I had to add the
> mod_dav.h to the include files (because it's not in the include directory).
>
> I parses the function correctly, but not the callbacks. As far as I seen,
> you don't create t
On Fri, 25 May 2001, barries wrote:
> That way the $r->add_xxx_filter( $name, $ctx ) DWIMs what to do with
> $ctx.
sounds good.
> What do you think of enabling Apache::Filter instance subclassing, given
> that filters have to inherit from it anyway to get the CODE attrs
> working?
>
> Seems
Since you've done the tieing STDIN/STDOUT bit in the past (1.x), why not
tie STDIN and STDOUT in modperl_output_filter_handler()? That would make
filter sub code bit less funky:
sub handler {
while (<>) {
print uc ;
}
}
STDIN/STDOUT would then be restored to their
>
> the current tools should work for generating a mod_dav backend with 2.0
> i think we just need to add the dav_ prefix to Apache::ParseSource so
> mod_dav.h is parsed into the Apache::{Function,Structure}Table.
>
I tried this already. Addtionaly to add the dav_ prefix, I had to add the
mod_dav
