Geoffrey Young wrote:
> Stas Bekman wrote:
>
>>Somebody at p5p was asking about problems with 5.7.3 and modperl 1.x.
>>I've run make test and got a bunch of failures, though didn't get a
>>chance to investigate.
>>
>
> with the AUTOLOAD stuff fixed, I'm back to compiling bleedperl and
> mod_perl CVS nightly, though I don't play with it every day as I used
> to.
>
> regardless of the failing tests it seems to work ok - I can complile,
> start the server, and do mod_perl stuff.
>
> the only thing I've noticed is that print "foo" doesn't seem to work
> but $r->print("foo") does - I figured something about the TIEHANDLE
> interface changed, but I didn't track it down. it might have fixed
> itself since I last looked.
Yup, here are some insights from N I-S:
From: Nick Ing-Simmons <[EMAIL PROTECTED]>
Subject: Re: Does mod_perl work with 5.7.3?
Mike Guy <[EMAIL PROTECTED]> writes:
[snip]
>Before leaving, my colleague said it looked like the problem was
>something to do with tieing *STDIN and *STDOUT, which mod_perl does
>from C code.
Tk's fileevent does likewise and also needed tweeking for 5.7.*
The problem is that 5.6.* applied tie magic to the GV * , and 5.7.*
applies it to the IO *. So if - like TK - your C code did io ops
on the IO expecting to access the "inner" untied IO with 5.7.* you instead
recurse back into the tie code.
--
Nick Ing-Simmons
http://www.ni-s.u-net.com/
_____________________________________________________________________
Stas Bekman JAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide http://perl.apache.org/guide
mailto:[EMAIL PROTECTED] http://ticketmaster.com http://apacheweek.com
http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
