On 7/6/07, Michael O'Keefe <[EMAIL PROTECTED]> wrote:
>> > They all differ slightly and therein lies the problem.
>> > XML may be bloated. But is far better standardized than
>> > any of (note several subtly different) examples given.
>>
>> The reason is there are many implementations of a very simple KEY VALUE
>> parser. Some more robust than others.
>
> And also each is different because nearly
> every KEY VALUE syntax is subtly different.
> Between you and Stremler four of five formats
> were produced in minutes. Multiply that by
> many intelligent people and you have a recipe
> for chaos; really Bable.
We've had "win.ini" config file formats for years in the testing group
and they are a PITA for anything other than simple configurations.
Arrays and complex structures are ridiculous in the "win.ini" format
Agreed. If there is a decent candidate for simpler
it is IMNSHO JSON. Well documented, has standard,
easy to read. There are parsers available in just
about any language you can think of. See
http://json.org/
BobLQ
--
KPLUG-List@kernel-panic.org
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
