On 20.01.2011, at 10:24, Fabien Potencier wrote: > On 1/20/11 10:04 AM, Lukas Kahwe Smith wrote: >> >> On 09.01.2011, at 17:51, Victor Berchet wrote: >> >>> There might be a better way to disable compilation by modifying the >>> framework bundle, >>> I'll propose it in a coming PR. >>> >>> On Jan 8, 6:19 pm, Victor Berchet<[email protected]> wrote: >>>> It much easier not to use a compiled version of the kernel classes >>>> while hacking the sf2 core (in order to be able to set breakpoints and >>>> trace human readable code). >>>> >>>> Is there a specific reason why the call to >>>> ClassCollectionLoader::load() is not wrapped in a if (!$this->isDebug) >>>> {} block in HttpKernel/Kernel.php ? >>>> >>>> I can see no visible impact (> 1ms) on the response time while not >>>> using compiled classes in dev mode. >>>> >>>> Thanks for your inputs, >>>> Victor >> >> >> Yeah, I am also not sure if this is a good practice. > > As I said before, the development env should be as close as the production > one, to avoid different behaviors. > > That's one problem we have in symfony1. This is related to the order the > classes are loaded and the interaction with the autoloader. > > If you hack on the core, you should be able to temporarily disable this by > tweaking the Kernel class.
Yeah, I do agree on that point. I guess one can always "disable" this behavior for one request by clearing the cache. regards, Lukas Kahwe Smith [email protected] -- 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
