Bob La Quey wrote: > > 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/
Still too complicated, and too ugly. I was just working on a simplified sytax, and it, too, is complicated on paper. It looks better as actually implemented, though. Remember: config files, with few exceptions, should be replacing command line options. Command line options should override the values in the config file. If you are needing to pass large amounts of UNICDE data in a config file, perhaps you need to completely rethink the config file to begin with. Configuration files should be easy to read, and easy to parse. I cannot think of any configuration format easier than KEY=VALUE. Except maybe KEY. But then =TRUE is implied. System programs get to violate this rule, a little bit, as system programs are not configured by users. They should still not need to be overly verbose, such as requiring a paragraph of quoted text. -john I still have the format I was working on. It uses a lot of C construction, such as C string escapes, and "string""continuation" concepts. I kept with # style comments instead of /* */. I don't care much for // comments in a configuration file. I think the biggest ``innovation'' is specifying network byte order for consecutive hexadecimal octets. -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
