On Fri, 2004-09-17 at 17:04, Cees Hek wrote:
> Another solution is to just reuse the teardown method, and be sure to call
> $self->SUPER::teardown within any teardown method you create. This will walk
> up
> the inheritance tree and execute the teardown method of the superclass.
>
After looking at my situation some more I think what I'm going to do in
my subclass is something like this:
sub run {
my $self = shift;
my $output = $self->SUPER::run(@_);
$self->cgiapp_finish;
return $output;
}
That way I get the hook I want and the CGI::Application module that I
use as a base class doesn't have to be modified.
Thanks for all the suggestions I got and I am still planning to release
this sub class once I'm ready.
--
Tony Fraser
tony@xxxxxxxxxxxxx
Sybaspace Internet Solutions System Administrator
phone: (250) 246-5368 fax: (250) 246-5398
---------------------------------------------------------------------
Web Archive: http://www.mail-archive.com/cgiapp@xxxxxxxxxxxxxxxxx/
http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: cgiapp-unsubscribe@xxxxxxxxxxxxxxxxx
For additional commands, e-mail: cgiapp-help@xxxxxxxxxxxxxxxxx
|
