> > You can change INCLUDE_PATH as often as you like. Admittedly, > > the docs don't make this very clear, but it is an Officially > > Approved Technique. I change it once per request, but as I > > suggested in my last mail you could change it in your > > Context::visit() method.
This is the way I originally did it, but what I'm doing in my current version is making the search to INCLUDE_PATH just another Strategy, and INCLUDE_PATH is unmodified (it's not even re-rooted to NAGA_APP_ROOT at runtime, it's done at initialization time). The climbing behavior is now done with a strategy that requires information from the Context. The neat thing is that Documents can now contribute their own Strategy if the policy is configured to allow it (In Naga, most boolean options like EVAL_PERL and ABSOLUTE and so forth can now take a list of patterns that the pathname is matched against. I intend to do work on a Policy class to expand on this idea, but it's not a priority). __________________________________________________ FREE voicemail, email, and fax...all in one place. Sign Up Now! http://www.onebox.com
