thanks, I'll add this for 1.22.
On Tue, 2 Nov 1999, Yasushi Nakajima wrote:
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,
On Thu, 28 Oct 1999, Yasushi Nakajima wrote:
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);
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]
Kyoto,
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 =
I think a better solution would be to make PerlRun use real object-oriented
thinking (method handlers), something like this:
sub handler ($$) {
my($class, $r) = @_;
my $pr = $class-new($r);
...
}
My personal philosophy is that any given class's name should only
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 $pr =
