Hello.
For those that know i'm making a Sound Engine.
But, I need to add a configuration file where the user can set there preferences.
So I was wondering what style would be preferred: (Ignore the content of the format, but look at the syntax in witch the data is represented)
(if unsure DON'T vote please)
Example of YAML
Example of S-exp
Example of XML
Example of JSON
This is the dataset i need to store

Code: Select all

{Setup1 %
     Headphones {
          headsize=12cm;
          headtype=a;
     }
}
{ Setup2 %
       Speakers {
            Count 4
             Speaker 1 {
                     5 degree; 50cm
              }
         }
}

Plain INI file type syntax perhaps? What more than key/value pairs do you need?

kyre's suggestions:

Code: Select all

Setup1:
  Headphones:
    headsize=12cm
    headtype=a
Setup2:
  Speakers:

Code: Select all

Setup1 = {
  Headphone = {
     headsize=12cm;
     headtype=a;
  };
};

So are you going with ini?

Open for discussion

I'm for XML in this regard just because there are so many tools for handling XML. Any modern program language has modules for handling XML which will allow the configuration to be handled by just about anything.

Ed wrote:...because there are so many tools for handling XML.

What if peaple don't desire to use any of these ?

Yes, XML may be nice to parse, but is awful for users to edit.

i vote for INI too, but i hope we will never need to edit it anyway

Morphed wrote:i vote for INI too, but i hope we will never need to edit it anyway

For now yes ... later you should get a GUI for it ...

YAML... lol
the only time i was confronted with yaml was porting somethign to osx... and yaml sucked there ...
probably my fault
nevertheless, I vote for XML

lua if you are not going to auto create config files
(maybe lua is over kill for just a config file)

simplified yaml with '>' instead of ' '

I have the feeling most choice Yaml for the readability.
Kyre's suggestion seem the best.
So can most agree on this ?

Code: Select all

Setup1:
  Headphones:
    headsize=12cm
    headtype=a
Setup2:
  Speakers:

Tabs will be used for intending. If the selection betweens tabs or space gets to hot i'll start the config file with:

Code: Select all

Intending: 4 space

OR

Code: Select all

Intending: 1 tab