> The bottom line is that I am asking for the breakdown of run() into > run_mode() and output_mode() to become a permanent part of the module. Then > I can overload run() without losing much at all in the way of upgrade ease.
Ah, this now becomes more clear. Okay, so what kind of impact would such a change have? (stream of consciousness follows) For reverse compatibility, run_mode would have to become what you refer to as output_mode. A new mode, say, logic_mode would have to be introduced. run() would call the indicated logic_mode() (with an empty default case), then call the indicated run_mode() and output it's return value. Heck, for the truly intense, run() could call an output() routine, which by default prints the output & headers, but could be overridden. I like this idea, I think it plays to CGI::Apps strengths, but we are adding some overhead to everyone. Did I summarize your hopes correctly? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
