Quote from: eri0o on Fri 19/07/2024 00:52:10I just did it to myselfAfter looking more closely at IniFile2, it's not exactly written in the same spirit -- so I would say the two modules are complementary. Plus, as I wrote, yours shows the way to "modern" approaches. No regrets!
Quote from: eri0o on Fri 19/07/2024 00:52:10perhaps there is some smart way to create an AGS dictionary from an INI file and also to serialize a dictionary to an ini file
Just my two cents:
Spoiler
If you want to make String-manipulation and String-parsing lovers happy, I think you should instead focus on creating String.Split(delimiter), Array.Sort, Array.Min, Array.Max (At least for primitive types: int, float, char, String -- case-sensitive and case-insensitive...). And (if at all possible!) make String.Char faster (for reading) and String.Append faster (for writing).
I would never have suggested that before, but now that you've created pseudo-properties on dynamic arrays (.Length), it's opening a world of possibilities.
Side Note: It will not only allow new powerful parsing capabilities, but Array.XXX will probably help a lot in pixel-manipulation modules too, which are hindered by the scripting language's speed. That's how Python and GDScript worked around the speed problem: by wrapping fast c++ methods and exposing them to the scripting API.
I would never have suggested that before, but now that you've created pseudo-properties on dynamic arrays (.Length), it's opening a world of possibilities.
Side Note: It will not only allow new powerful parsing capabilities, but Array.XXX will probably help a lot in pixel-manipulation modules too, which are hindered by the scripting language's speed. That's how Python and GDScript worked around the speed problem: by wrapping fast c++ methods and exposing them to the scripting API.
[close]