Re: A standard package for config files is needed

[tmoran@acm.org]

>The Java Property class is simple and easy to use! The Properties
>can be stored as an ASCI File, which is a  List of (Key,Value) pairs.
  In the Windows Registry case, the data is never accessed directly, so it
doesn't matter if it's ASCII or whatever.  If you are going to allow safe
concurrent access, the config file obviously can't be a simple ASCII file.
Instead there's a database manager frontend (nee regedit) to allow low
level mucking, and most changes are normally done via API calls under the
control of the relevant app itself.
Looking at Claw, I see, eg,
        -- Typical usage might be:
        --     Claw.Registry.Get(
        --           Root_Key   => Claw.Registry.HKEY_CURRENT_USER,
        --           Subkey     => "Software\MyCompany\ProgramName",
        --           Value_Name => "User_Nickname",
        --           Item       => Saved_String,
        --           Last       => Last);
and appropriate variations for stream io, record io (a la Sequential_IO),
etc.  Note also that Windows has the concept of branches of the
configuration tree for Users, Current_User, Local_Machine, Current_Config,
etc.  That's useful and should be considered for inclusion.