Another, simpler option to avoid mantaining all the fake classes would be to throw a clear exception when a intl class is used explaining the error and giving some links to help download and install the intl extension depending on the user OS (maybe hosted in a special section in symfony-reloaded.org). It may also give directly the link to the exact extension the user should install by detecting its php version and also the location of its php.ini. The central repository of the compiled intl extensions could also be hosted on the s2 site.
Its not the perfect solution neither, but it will save lots of time to the developers maintaining a parallel implementation of the intl classes. -- 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
