Sounds like a rabbit hole to me, but maybe you've thought it through more than I have. For example, how would this work if one service relies on the same class as another service?
Setting the idea of smart compilation aside, adding calls to require_once to the PhpDumper might be a good idea so we don't have to get into the autoloader. This would have to play well with ClassCollectionLoader, of course. k -- Kris Wallsmith | Release Manager [email protected] Portland, Oregon USA http://twitter.com/kriswallsmith On Feb 2, 2011, at 1:05 PM, Johannes wrote: > I'm not sure if this was investigated at some point, but since the DIC > allows us to determine the dependencies between the different services > easily, we could compile the class/interface files for all dependent > services/classes into one file and load this one file before a service > is instantiated. > > Since I haven't done any tests, I don't know how much we could gain by > this, but it would certainly save some round trips via the auto-loader. > > -- > 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 -- 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
