Hi Michael
I'm beginning to understand this neat module, and have a couple of comments:
(1)
Line 330:
$app->mode_param(sub { return $rm }) if( $rm );
What happens in my apps when I already have sub setup containing:
$self -> mode_param(\&setup_mode);
<predicted_answer>
Patient: Doctor! Doctor! It hurts when I do this!!
Doctor: Don't do that...
</predicted_answer>
But seriously, folks.
(2)
I assume there are - in very simple terms - 2 ways to structure an app:
o One monolithic script
o One (Perl) module per run mode, with common code in a parent
The latter obviously avoids loading code for run modes which are not being used,
but (for small apps especially) is there any other reason to structure things
that way, apart from personal preference?
--
Ron Savage
[EMAIL PROTECTED]
http://savage.net.au/index.html
---------------------------------------------------------------------
Web Archive: http://www.mail-archive.com/[email protected]/
http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
