3 ms·
> e.g. tests, type checks or other static analysis You can do all these things for YAML or JSON or TOML or XML or INI or s-expressions or custom bytecode or bu
by yellowapple 7y ago
> e.g. tests, type checks or other static analysis
You can do all these things for YAML or JSON or TOML or XML or INI or s-expressions or custom bytecode or butterflies or however else you're defining configuration data, too. It might not be present as part of the configuration language itself, but that's true of a lot of full-blown programming languages, too (especially the dynamic and weakly-typed ones).
If anything, a static configuration file should be easier to statically verify than a full-blown programming language because it's, you know, actually static. This goes out the window somewhat with YAML or XML (which do somewhat funny things), but once you have that hash table or whatever you've deserialized the config data into, congrats, now you can statically analyze it.