4 | | I'm referring to how it's implemented now, there is no central definition of valid command line options. The engine doesn't validate them until it needs them, which is bad, and adding a help message at each point would be a bad idea. Instead, there should be a library which handles this for us (preferably with options and help defined in some flexible, standard format stored in data file). |
| 4 | I'm referring to how it's implemented now, there is no central definition of valid command line options. The engine doesn't validate them until it needs them, which is bad, and adding a help message at each point would be a bad idea. Instead, there should be a library which handles this for us (preferably with options and help defined in some flexible, standard format stored in data file). As options get parsed and validated, they go into a centralized config system, later the program can use them knowing that they are OK. |