Tim Colson wrote:
>
> I'd say your example shows a real-world situation using the action chaining
> I'm talking about. Just seems a bit of a kludge to have an 'eval' doing your
> dirty work. <grin>
I agree. What about adding another run mode to CGI::App to handle this.
It might make my example look like this:
return $self->return_rm($FORM{return_rm}, @args_to_pass_to_run_mode);
That would just be some syntactic sugar to rewrite the eval statement.
On the one hand I think it's "cleaner". On other other hand, it's just a
few less
characters to type, but using "eval" means I have less API to learn,
which is one of things I like about CGI::App -- simple interface.
I've learned that sometimes creating slightly cleaner syntax at the
expense of additional complexity
doesn't always turn out to benefit me in the long run. So I'm torn. I
think if it was
in there, I'd use it. :)
-mark
CGI::App driven home site rendered as static pages:
http://mark.stosberg.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
