>
> Heck, for the truly intense, run() could call an output()
> routine, which
> by default prints the output & headers, but could be overridden.
>
> I like this idea, I think it plays to CGI::Apps strengths, but we are
> adding some overhead to everyone. Did I summarize your hopes
> correctly?
>
>
Yeah, that sounds right. My original idea was for the base class to look
something like this:
subroutine run {
my $rm_output = action();
return output( $rm_output );
}
where action() was a (private?) subroutine that invoked the correct run_mode
call and output() formatted and printed the output. In this way the current
implementation of run is not altered in the least - just modularized a
little.
What is gained is that overriding run() is now a much less daunting task.
Elizabeth
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
