On Thu, Feb 22, 2001 at 10:04:01AM -0800, William Lee wrote:
> I don't think the search order I'm looking for is really in violation of
> the old one. The "overriding" behavior is still the same at the top
> level directory (Index falls to Default). It's just that when you look
> for the class in the parent directory, you need to for the class with
> the same name first.
But then you have the ambiguous question of what happens if there's no
Index class in the right package, but there is a Default class, and
there is an Index class in the parent package? Some people would expect
and want the Default class to be used (as per current behaviour) whereas
I'm guessing you'd like the parent Index class to be used...
so I'd be -1 on this change as stands. Having said that I see what
you're tring to achieve, and like the idea. Perhaps we need a more
explicit mechanism for handling multiple language templates...
If I have a brainwave I'll let you know :-)
--
Sean Legassick
[EMAIL PROTECTED]
Soy un hombre: nada humano me es extrano
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
