Hi Folks On Thu, 2009-06-18 at 01:00 +0200, Rhesa Rozendaal wrote: > Richard Jones wrote: > > Richard Jones wrote: > >
[snip scary code] > The hashref goes into the first var, because it's being passed in > positionally. The fourth variable gets the id from the query, because it's > named $"id" in the signature. It's still a normal method call, so > $self->edit(1,2,3,4) would result in $foo=1, $bar=2, $errs=3, $id=4. It's > only > when you don't supply arguments that the query param fallback comes into play. > Of course, with dfv you're going to see a mix of that, and that makes it a > bit > harder to figure out what's going on. Surely this is a maintenance nightmare! And what happens if someone else has to patch this sort of stuff? Does the problem really lie with the adoption of RunmodeDeclare in the first place? I'd suggest, Richard, you seriously consider ditching it, for the sake of sanity and simplicity, at least. But keep CGI::Application::Dispatch. You're on a winner there. -- 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/ ## ## ## ################################################################
