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
I know this isn't a CGI::App based solution for your problem, but
consider WWW::Pipeline's (a subclass of Application::Pipeline) solution
to adding a new hook. It's as simple as adding entries to an array in
the appropriate slot of a hash called the %plan. Here's the superclass'
plan:
our
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.
I thought about doing this but then it puts the onus of remembering
On Fri, 2004-09-17 at 17:04, Cees Hek wrote:
The extra hook you have added looks like it occurs immediately after the
teardown hook. So it doesn't look like it realy adds a new location for a hook,
since a simple teardown hook will do exactly the same thing.
This is true at first glance but,
Tony Fraser wrote:
On Fri, 2004-09-17 at 17:04, Cees Hek wrote:
The extra hook you have added looks like it occurs immediately after the
teardown hook. So it doesn't look like it realy adds a new location for a hook,
since a simple teardown hook will do exactly the same thing.
This is true at
Hi,
I'm developing a reusable subclass of CGI::Application. For this project
I would like to have a new hook added to CGI::Application.
The attached patch includes the changes I have made to my local copy for
development. If anyone has any suggestions or anything please speak up.
Otherwise, I'd
Quoting Tony Fraser [EMAIL PROTECTED]:
Hi,
I'm developing a reusable subclass of CGI::Application. For this project
I would like to have a new hook added to CGI::Application.
The attached patch includes the changes I have made to my local copy for
development. If anyone has any
