From: Kurt H. <kh...@ch...> - 2004-04-17 04:15:14
|
Thanks for responding so quickly, Jon and Dave! Even if it confirmed what I feared...:-( > On Fri, 16 Apr 2004, Jonathan Swartz wrote: > >I don't think we were aware that anyone was using this feature! Thus it got >only an unglamorous mention in the Changes file: > >- ** The Interp's use_autohandlers, use_dhandlers, and >allow_recursive_autohandlers parameters have all been removed. > >May I ask why you use autohandlers in this way (so that they only affect a >single directory)? Perhaps we can think of a workaround. Initial conditions, I think. It was the default behavior in Mason when I started using it in version 0.7x. I never quite wrapped my mind around the recursive functionality until I read Dave's book last fall. So, I've developed around the non-recursive. I assign different subdirectory trees to clients and change functionality and look based on the directory. It's just easier to organize things and for clients to remember where things are. Here are some examples: https://ssl.charityweb.net/mercycorps/ https://ssl.charityweb.net/mercycorps/carboncounter/ #diff look/func https://ssl.charityweb.net/mercycorps/card/ #diff functionality or https://ssl.charityweb.net/psr/ https://ssl.charityweb.net/psr/event/register.htm #diff look/func https://ssl.charityweb.net/psr/pana/event/register.htm #diff look > Dave Rolsky wrote: > > We already have one nasty workaround, which is add this: > > <%flags> > inherit => undef > </%flags> > > to every autohandler. This can be done via a script pretty easily, I'd > think. Yes, I saw that. I was just hoping there was something I could do without editting all the autohandlers via a script. I guess not, eh? Take care, Kurt kh...@ch... |