Anonymous user
Talk:Read a configuration file: Difference between revisions
History of the file format, and the reasoning behing the two comment symbols
(→"Standard": Agreed.) |
(History of the file format, and the reasoning behing the two comment symbols) |
||
Line 26:
: It would probably be better to formulate similar as "read a config file according to your language standard, extra credit for INI, Java property and XYZ" --[[User:Jofur|<Jofur>]] 20:11, 16 February 2011 (UTC)
: Agreed as well. I'd also be interested in seeing if there are configuration formats which can be parsed based on run-time-consumable grammar definitions. --[[User:Short Circuit|Michael Mol]] 20:23, 16 February 2011 (UTC)
This was very similar to the .INI format, before the boxed section headers were introduced. I developed that into a brief specification entitled "Standard Configuration File Format" which I wrote back in 1991.
The reason for the two comment symbols is that the hash symbol is a permanent comment and cannot be manipulated automatically. However, a leading semicolon may be removed or placed by automatic software reconfiguration tools.
A related task to this one, which I have not yet written up is to comment out or uncomment one of the parameters.
[[User:Markhobley|Markhobley]] 00:47, 21 February 2011 (UTC)
| |||