I think you are mistaking your data for your code. Others have noted that this is a workflow process. In my day job I address this sort of problem with Lotus Workflow. The idea there is to write down the whole workflow process separate from your application and let the workflow engine do all the actual execution. (follow the link and do a brief scan of the product brief PDF to see the pretty pix). This isn't a new concept - it's just separating your data from your code.
I haven't seen anything in the perl world that even approaches LWF so that's a miss. If you can find a comfortable medium between writing an workflow engine and just hardcoding your workflow you'll be good. Anyhow, I just wanted to point out that you had the wrong orientation.
Fun Fun Fun in the Fluffy Chair
In reply to Re: Decision Trees and the Strategy Design Pattern
by diotalevi
in thread Decision Trees and the Strategy Design Pattern
by djantzen
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |