On 9/9/05, Dave Howorth <[EMAIL PROTECTED]> wrote: > What's confusing me? Well first, the comment - it's ALWAYS a template > isn't it? Never a static page.
If there's an error during call_authenticate(), then error() will get called, and at that point you might still be dealing with a static page. > > I can't see any reason not to just delete that 'rough test'. It doesn't > seem to do anything useful. And if it isn't there, I expect I'd get the > nice page explaining there were problems finding a template. But my > brain hurts, so I'd be grateful for any other thoughts. There are so many side-effects and so much coupling of distant methods with each other that I've never been able to get my head around Maypole's exception system. Either it's very clever and I don't get it, or it's a mess that needs fixing. d. ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Maypole-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/maypole-devel
