Hi Richard

On Thu, 2009-06-18 at 09:31 +0100, Richard Jones wrote:
> Rhesa Rozendaal wrote:
> 
> >> It was designed to just get OP (Original Poster) to re-think /his/ line
> >> of attack :-).
> > 
> > Good point. At the very least it prompted me to suggest yet another 
> > approach.
> > Ar you still with us, Richard? :-)
> 
> Wasn't then (02:52 GMT) - am now. It's true I've had a few issues with 

Just in case you think I'm a night owl too, it was 11:09 am when I
posted... That's what you get for being at the center of internet, aka
Melbourne, Australia :-).

> RunmodeDeclare in the past, but always because I've misused it. Your 
> suggestion not to use signatures on run modes and to fetch query params 
> traditionally, or alternatively only declare positional arguments, are 
> both consistent with maintainability IMO, provided it's documented 
> locally in the application, so I can remember how it works when I come 
> back to it in future. That's really the issue here I think - 
> understanding (and remembering) how RunmodeDeclare (and 
> Method::Signatures) actually works.
> 
> So in answer to Ron's nuclear option, I'm not persuaded it's necessary 
> to bin it at the moment. But in reality I use it only for the admin 
> parts of my app, as it was too much work to re-factor all the rest of it 
> away from AutoRunmode, which was and is working fine anyway.

Fair enough. I'm deeply uneasy about adding these modules on top of
things, myself, so I don't.

-- 
Ron Savage
[email protected]
http://savage.net.au/index.html



#####  CGI::Application community mailing list  ################
##                                                            ##
##  To unsubscribe, or change your message delivery options,  ##
##  visit:  http://www.erlbaum.net/mailman/listinfo/cgiapp    ##
##                                                            ##
##  Web archive:   http://www.erlbaum.net/pipermail/cgiapp/   ##
##  Wiki:          http://cgiapp.erlbaum.net/                 ##
##                                                            ##
################################################################

Reply via email to