Re: Problems with the fix for the BC break introduced in 5.4.29 and 5.5.13

Hi! > yeah, that would work ofc, but as these libs seems to have instanitate > arbitrary classes, that would require either generating files on the fly > and including them or simply evaling them, but of those are a bit > dirtier than using Reflection for the same job. True but that's what phpunit, etc. are doing for mocks anyway, aren't they? > true, but it can also be used to argue for loosening the restriction, > why restrict something from Reflection, which is already possible from > simple class extension. I agree, probably makes sense to allow it if you can do it anyway. Reflection is not something you can trigger without explicit codding (unlike O: thing) so it's fine with me. > a nice thing from OOP POV and also will cause problems if/when we > introduce a reflection method removing final from classes/methods (this > was already proposed not that long ago with a working patch but was > turned down because other reasons). That probably wouldn't be a good idea, especially for internal classes. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/