If you have a look at the core classes, they depend less and less on sfConfig.
The core classes must be usable without symfony, so they tend to take an option array in the constructor. So, for example in symfony 1.1, all options for the factories have been moved to the factories.yml file (as it makes sense). That said, I'm not sure we will be able to phase out the sfConfig anytime soon but symfony relies less and less on sfConfig. Fabien -- Fabien Potencier Sensio CEO - symfony lead developer sensiolabs.com | symfony-project.com | aide-de-camp.org Tél: +33 1 40 99 80 80 Carl Vondrick wrote: > Hello, > What is the future of sfConfig (not sfConfiguration)? Will its static > methods eventually be phased out for sfConfiguration's member methods, > like ->getRootDir()? > > Thanks, > Carl > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
