Quote:
Originally Posted by 73ChargerFan
What is wrong with an ini file? He's already got a directory full of DLLs and a PlugIns directory.
|
1. All those DLLs and Plugins are to be
READ ONLY
2. Update process is much easier -> just overwrite target files with the new ones and you're done, there's no need to keep INI file and watch for its compatibility across future versions of eac3to
3. Implementation of INI parser into existing source code means much more work than adding one more CLI switch
4. Unless there is significant amount of configuration options needed for application then it's better to stay away from INI/registry altogether
5. GUI add-ons can easily adopt any new CLI option and keep it along with many other settings in their own INI files if necessary