Yeah, we have a little clash of terms here.
I thought you were talking about the ini file resaved as Unicode.
My bad.
In any case, TC shouldn't skip remaining entries if the first one is "empty".
<Offtopic>
MVV wrote:Registry it's a pain for portability. I prefer INI files because they are simple and I don't need to re-configure every program when I reinstall Windows.
The point was that the functions are outdated since at least 15 years,
not that Ini files are bad in general.
We'd probably have seen some updated functions with loosened limitations if MS would still have
interest in config file handling.
MVV wrote:Quite simple wrapper function allows retrieving strings as objects so it isn't a reason for C-Style.
The API itself is C style. So you need buffer allocations and have unnecessary (multiple) data copy.
In portable C++ with custom ini parsers you could just open a file stream and let the CRT handle everything.
MVV wrote:INIs (just like registry) are not for huge data, they are for configuration parameters.
Large binary data must be stored in separate files (e.g. in databases)
I didn't mention binary data.
Just look how much keys some MS programs (Office...) store in the registry
when installed. It regularly exceeds 1 MiB.
Ini files are just an (old) serialization format, like XML/JSON/YAML today, but far more "human readable".
But a config can be complex too, having thousands of entries, exceeding that 64k per section easily.
TC uses that format, and therefore all it's limitations.
</Offtopic>