Luis Garrido schrieb: > To be utterly pragmatic, I think at this moment the best approach for > this problem would be an evolutionary one. > > Just implement whatever format you feel like and see if it takes. No > one is going to sue you, although you are guaranteed to get your fair > share of critics, no matter what. > > At the worst case, this particular situation is so utterly simple that > it should be trivial to convert one format to another if the need > arises. > > If it helps in the end I chose for my project INI files just because > it was a Qt app and Qt provides a nifty INI parser (QSettings) with > some merging capabilities (concurrent Qt processes can make changes > without corrupting the file and those are easily synchronized.) But > that was me just being lazy, I guess.
In fact, being lazy can be good. INI files nearly use a YAML syntax which is also very easy to parse with C, C++, python and perl. -- Marc-Olivier Barre -- --- MarcO'Chapeau ---- - www.marcochapeau.org - _______________________________________________ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
