Iniparser Rewrite #2012
Comments
EvilGuru uploaded file |
Per commented I would love to hear why you rewrote it, and how it is different. And why you hate comments so much ;-) |
dak180 changed _comment0 which not transferred by tractive |
EvilGuru commented The old one made it very difficult to work with sections as you had to go and prefix everything so:
requires "foo:bar" as the key. If you're dynamically generating sections (as I do for stored templates) this is a pain as you need sstrcat calls all over the place. So far as the design went: the dictionary/iniparser distinction was annoying. As were the some of the function names like As for why I hate comments: no comment. (But you saw that coming, now, didn't you ;) |
Safety0ff uploaded file |
Safety0ff commented ini2.diff Fix challenges by converting key's to lower case (since they are converted to lower case in iniparser_line) Note: I didn't fix all possible case sensitivity issues! Changed PHYSFS_fgets and stuffed it into physfs_ext.h. Added prototypes for utility functions and put them at the end of the file. |
Safety0ff uploaded file Added Case insensitivity unit test, added case insensitivity to sections |
Safety0ff uploaded file Improve case insensitivity selftest |
EvilGuru uploaded file Updated patch; better error handling and documentation. |
EvilGuru commented I've uploaded an updated version of the path. If there are no further suggestions I'll commit it sometime tomorrow. P.S. The original author needs to look up the term "buffer overflow." |
anonymous uploaded file |
anonymous uploaded file |
Per changed status from |
Per changed resolution from `` to |
resolution_fixed
type_patch (an actual patch, not a request for one)
| by EvilGuruAttached is my rewrite of the iniparser. Included with the patch are unit tests (which must be run manually as adding them to src/main.c causes them not to execute on account of prior tests failing) and a port of existing iniparses users.
Feedback welcome.
Issue migrated from trac:2012 at 2022-04-15 22:08:45 -0700
The text was updated successfully, but these errors were encountered: