Description:
------------
---
From manual page: http://www.php.net/function.parse-ini-file
---

Though this is a simple request, I think being able to load and save ini files of this format will increase application portability in the long run for many people. If there were also a way to somewhat augment the parsing schema, to catch other common *nix .conf files, t'would be pretty nice.

Test script:
---------------
<?php

//Load my own configuration file for the user running this app
$ThisAppnConfig = parse_ini_file('~/.MyApplication');

//Load the global configuration for some package used in this app
$SomeAppConfig = parse_ini_file('/etc/SomeApp/default.conf');

$ThisAppConfig['SomeApp.host']=$SomeAppConfig['host']
$SomeAppConfig['host']=$ThisAppConfig['host'];

//Update the user's settings to be compatible with my app
save_ini_file($SomeAppConfig,'~/.SomePackage');

//Save the old value in case the user needs it
save_ini_file($ThisAppConfig,'~/.ThisPackage');

?>

Expected result:
----------------
After loading and parsing two, standard configuration document, the developer uses values and may or may not transfer them to/from other config files with the same format.

At the end, a configuration file is generated from the associative array supplied. 

The only caveat is that on saving, a diff tool should be employed to align any pre-existing key/values to their same line number. By only appending new data to the end, we preserve any user-provided comments as well.

Would also be nice to have similar nesting detection both ways. I,e providing the following..


Array
(
    [first_section] => Array
        (
            [one] => 1
            [five] => 5
            [animal] => Dodo bird
        )

    [second_section] => Array
        (
            [path] => /usr/local/bin
            [URL] => http://www.example.com/~username
        )
)

Works as expected to append/replace within a section before falling back to file append.

Actual result:
--------------
None, feature request.