Doug> the handler() in Apache::PerlRun was not originally indended to be
Doug> subclassed. however, if somebody submits a patch to make is
Doug> subclass-able that doesn't break the way Apache::PerlRun currently works,
Doug> that would be fine.
Following modified code works itself and as derived
Ken> That's only one way of calling a handler. The other way is to use method
Ken> handlers, which lets you inherit methods from base classes. See the
Ken> documentation in mod_perl_method_handlers.pod for more info.
I see at all. Thank you for your help.
Sey Nakajima <[EMAIL PROTECTED]>
Kyot
On Wed, 27 Oct 1999 23:24:58 -0500
Ken Williams <[EMAIL PROTECTED]> wrote:
Ken> I think a better solution would be to make PerlRun use real object-oriented
Ken> thinking (method handlers), something like this:
Ken>
Ken> sub handler ($$) {
Ken> my($class, $r) = @_;
Ken> my $p
Hello All
I have made a module derived from PerlRun. It overrides only readscript()
method in PerlRun. First I wrote as follows (essencial part only)
package Apache::PerlRunFake;
use Apache::PerlRun;
@ISA = qw(Apache::PerlRun);
sub readscript {
...
}
*handler = \&
