Fabien POTENCIER wrote:
> That's a great use case, indeed. So, we need to fix it ;-) Do you have a
> patch?
Well, whilst working on that... look what we found:
sfController.class.php
313
314 // fix for same name classes
315 $moduleClass = $moduleName.'_'.$class;
316 if (class_exists($moduleClass, false))
317 {
318 $class = $moduleClass;
319 }
320
So, this already works - but.. what we should do is remove the old
behaviour, having two classes with the same name should obviously not happen
--
Ian P. Christian ~ http://pookey.co.uk
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"symfony developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/symfony-devs?hl=en
-~----------~----~----~----~------~----~------~--~---
