generalized-language-modeling-toolkit
generalized-language-modeling-toolkit copied to clipboard
Config file paths shouldn't be hardcoded
The location where config files lie should not be hardcoded.
I agree but how would you want to resolve this issue?
I guess i will implement a command line argument that allows to specify a path to the config file. This has low priority though.
sounds good to me. do we have at least a "standard config file" in the same directory where the binary is and a good error message saying ether "provide config file at this path" or "use command line argument and point to it... check our manual to learn about the structure of the config file at github.com/...."