> > -----Original Message-----
> > From: Stas Bekman [mailto:[EMAIL PROTECTED]]
> > Sent: Wednesday, May 03, 2000 2:07 PM
> > To: Geoffrey Young
> > Cc: mod_perl list
> > Subject: RE: Why does $r->print() dereference its arguments?
> >
> >
> > On Wed, 3 May 2000, Geoffrey Young wrote:
> >
> > > interesing behavior - print behaves the same way...
> >
> > http://perl.apache.org/guide/porting.html#Apache_print_and_CORE_print_
>
> the guide is getting so big these days, it's hard to keep up with all the
> new developments. Or maybe that entered a few versions ago :) It's along
> way from the mini-guide that got me started...
That's correct. It was added in the last release
CHANGES:
04.09.2000 ver 1.22
* porting: added: "Apache::print() and CORE::print()" (Doug)
Well, it's been mini-guide, then it became just guide, now I'm going to
call it giant-guide :) Sorry about the size. I hear woes when there is no
documentation, and as well when there is too much of it... go figure out
:)
> > Under mod_perl CORE::print() will redirect its data to
> > Apache::print()
> > since the STDOUT filehandle is tied to the Apache module.
>
> yeah, I thought something like that was happening, but I wasn't sure about
> the mechanism - I recently saw that Apache::Filter will intercept print()
> but not $r->print(), so I wasn't sure what was going on internally...
Of course, it's because the two are basically the same under mod_perl, so
it doesn't matter which one you pick to intercept. Well, only one way...
$r->print() won't call CORE::print().
______________________________________________________________________
Stas Bekman | JAm_pH -- Just Another mod_perl Hacker
http://stason.org/ | mod_perl Guide http://perl.apache.org/guide
mailto:[EMAIL PROTECTED] | http://perl.org http://stason.org/TULARC/
http://singlesheaven.com| http://perlmonth.com http://sourcegarden.org
----------------------------------------------------------------------
