4 ms·
1. Comments 2. I like the separation of data and the program and am not the biggest fan of using a full scripting language as a config file (sometimes popular
by chunk_waffle 4y ago
1. Comments
2. I like the separation of data and the program and am not the biggest fan of using a full scripting language as a config file (sometimes popular js, php, and lua)
Bonus: Some way to specify variables for reusable values, not a deal breaker though.
Bonus 2: Not having to learn a radical new config file format.
- dan_linder 4y agoa big plus one for both these items mentioned. and annoyance I've encountered with some configuration files is the lack of a built-in comment line so I can communicate in line with the configuration decisions to a future user. Your comment about variables for usable values reminded me that it would be nice if the configuration file parser could reference other variables and sections of the configuration file to avoid repeating oneself in the same configuration file. for example, if the configuration files describing a fleet of virtual machines, it would be very handy to define small/medium/large system types with varying RAM, CPU counts, and disk layouts, then reference just the small, medium, or large type throughout the configuration file.
- logicallee 4y ago>Your comment about variables for usable values reminded me that it would be nice if the configuration file parser could reference other variables and sections of the configuration file to avoid repeating oneself in the same configuration file. How do you suggest specifying a variable?