In my opinion, I think XML should be the recommended route. Using some obscured version of a Windows origin configuration file and then bastardizing it belong belief to add functionality is the entirely wrong way to go.
XML and the newly added ZendFW XML namespace (in 1.9) is the right way. That's what XML was built for. Not INI. We should be discouraging bad practices. Bending a format into a direction it was never meant to go is not a good practice. --- Philip g...@gpcentre.net http://www.gpcentre.net/ On Mon, Oct 26, 2009 at 12:27 PM, Vincent Louvet <vinc...@e-spiration.com>wrote: > > Hi, > > Removing the 2 signs made the PHP errors disapear but the routes don't work > at all (they are just ignored which I think is normal bacause the regexp is > false then). > It is said that the INI support is improved in PHP 5.3, I just find it more > obscure. > > Discouraged, I finally swapped from ini to xml and everything is working > fine again. > > If someone is interested I can send key excerpts from the application.xml > (imho the doc shall be updated with more xml examples). > > With best wishes, > > > V > > > weierophinney wrote: > > > > > > I see one problem here already. It may or may not affect usage, but > > remove the leading '^' and trailing '$' -- the router adds those for > > you. Let me know what happens when you do that. If it works, great, if > > not, we then have a test case for the 5.3 test cases. > > > > > > > ----- > Vincent > -- > View this message in context: > http://www.nabble.com/application.ini-adaptation-for-php-5.3-tp25993786p26063920.html > Sent from the Zend Framework mailing list archive at Nabble.com. > >
