Perl-Sensitive Sunglasses | |
PerlMonks |
Re^5: Review: CGI::Prototypeby xdg (Monsignor) |
on Dec 30, 2004 at 06:44 UTC ( [id://418197]=note: print w/replies, xml ) | Need Help?? |
I don't think that's quite right. In both cases, the logic flow is
The difference is in the nature of (1) and the details of (2). I prefer to think about it this way:
For me, apart from style preferences, C::P works well where the validity conditions for entering particular states frequently depend on the current state. C::A is useful where the validity conditions for entering a particular state depend solely on the data requirements of the target state. If a C::A app always required a parameter for "current state" along with the "run mode" and used that plus other submissions to determine the state entered, it would provide the same functionality as C::P. C::P just enforces that kind of thinking from the beginning. -xdg Code posted by xdg on PerlMonks is public domain. It has no warranties, express or implied. Posted code may not have been tested. Use at your own risk.
In Section
Meditations
|
|