This would work, but Bernhard has persuaded me that it is a bad idea to provide an implementation of a missing PHP feature that other libraries might see and trust (because class_exists shows it) unless that implementation is 100% sound and you're prepared to deal with whatever might be asked of it. We're looking to do a stub implementatation of the Intl extension here, so Bernhard is right that in this case we should use a wrapper class instead and be consistent about using it.
On Jan 26, 12:48 am, Fabien Potencier <fabien.potenc...@symfony- project.com> wrote: > On 1/26/11 1:39 AM, Tom Boutell wrote: > > > To autoload implementations of the missing Intl classes all we need is > > a folder in autoload.php for things that unfortunately do not have a > > consistent namespace or prefix... > > Recently, I added a catch-all mechanism, where the autoloader looks for > the class in a directory (without prefix). Of course, we can only have > one such directory, so not sure it helps. > > Fabien -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com 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
