> So you are suggesting that a basic AUTOLOAD method exist by default to
> address the case of people submitting "rm=AUTOLOAD" when it doesn't
> exist?
Well, not exactly. By default there would be no behavioral changes to
how CGI::App works, but you could override the "cgiapp_autoload()"
method to create your preferred reaction.
(After reading what I just wrote above, that may not be the best way to
split autoloading out of the runmodes, but it's one way.)
> Perhaps you are suggesting that "AUTOLOAD" would be better handled
> outside of the run_modes() function, since it's not really a run mode
> itself? That makes some sense. However, considering it's already
there,
> it's convenient, and there seems to be a very marginal negative
> side-effect, I'm inclined to leave it alone.
Yeah, this is what I'm talking about. I agree that it's really more a
"semantics" issue than anything. I'm also inclined to leave it be -- but
it's something that came to mind at the time and I thought I should
mention it.
-Brian Cassidy
http://www.gordano.com - Messaging for educators.
---------------------------------------------------------------------
Web Archive: http://www.mail-archive.com/suppressed/
http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: suppressed
For additional commands, e-mail: suppressed
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.