personally I would prefer it if they are grouped - just as they are https://github.com/joomla/joomla-cms/blob/staging/installation/configuration.php-dist

?

It introduces inconsistency to how the Registry API dumps objects, and I'd say it's a behavior that isn't one that should be forced.

If you really want to pursue this...

• The sort option needs to be supported in all formatters
• It should probably be a configurable option that gets passed in when you instruct the Registry to export the contents to a file format
• Callers to that function then need to pass the right option

personally I would prefer it if they are grouped

That can't be done efficiently with what is in essence a code generator. I'd rather us use a proper Registry structure for the config though (so you have a `public $database => array('name' => 'db-name'); type structure) but that would be a massive B/C break as it relates to the configuration keys.

Yes I know we always disagree, but this is 3 lines of code change instead of huge amounts of change.

This class does more than just save configuration.php, it converts any registry object to a php class, and so has to be reuseable.

In fact the ordering should be configurable as well.

In fact the ordering should be configurable as well.

Like @mbabker says :)

So good idea, but bad implementation. Will revisit this when Im not so busy or stressed.