I've written a singleton class that encapsulates access to a particular ini file. It creates an IniConfigSource in its constructor, which is used within the various "Get..." and "Set" methods. Are there any pitfalls in using a singleton IniConfigSource as opposed to newing one up each time I want to get or set a setting?
The only problem I've encountered so far is where two different classes access the same ini file, but different sections. When I call Set() in one of them, it seems to overwrite any settings that the other class may have previously written, as though their respective IniConfigSources are caching the entire file, then writing the whole lot when Set() is called?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've written a singleton class that encapsulates access to a particular ini file. It creates an IniConfigSource in its constructor, which is used within the various "Get..." and "Set" methods. Are there any pitfalls in using a singleton IniConfigSource as opposed to newing one up each time I want to get or set a setting?
The only problem I've encountered so far is where two different classes access the same ini file, but different sections. When I call Set() in one of them, it seems to overwrite any settings that the other class may have previously written, as though their respective IniConfigSources are caching the entire file, then writing the whole lot when Set() is called?