BUGFIX
- Writer now understands UTF-8 BOM-encoded files. (#7)BUGFIX
- Fixes a bug introduced in 0.9.12 where reader would break when reading empty files.
BUGFIX
- Fixes parser breaking for UTF-8 BOM-encoded files. (#7)
BUGFIX
- Fixes various compiler warnings.
BUGFIX
- Change delimiter constants toconst char* const
to prevent unnecessary allocations. (#5)
BUGFIX
Adds missing cctype header. (#4)
BUGFIX
Avoid C4244 warning. (#2)
FEATURE
Adds case sensitivity toggle via a macro definition.
BUGFIX
Changed how files are written / generated. Proper line endings are selected depending on the system.FEATURE
Support UTF-8 encoding.
BUGFIX
Fixes a bug where writer would skip escaped=
sequences for new sections.
BUGFIX / FEATURE
Equals (=
) characters within key names are now allowed. When writing or generating a file, key values containing the=
characters will be escaped with the\=
sequence. Upon reading the file back, the escape sequences will again be converted back to=
. Values do not use escape sequences and may contain=
characters.BUGFIX
Square bracket characters ([
and]
) are now valid within section names.BUGFIX
Trailing comments on section lines are now parsed properly. Fixes a bug where a trailing comment containing the]
character would break the parser.BUGFIX
Values being written or generated are now stripped of leading and trailing whitespace to conform to the specified format.
BUGFIX
Fixes inconsistent behavior with empty section and key names where read would ignore empty names and write would allow them.FEATURE
Empty key and section names are now allowed.
BUGFIX
Fixes the multiple definition bug #1BUGFIX
Fixes a bug where awrite()
call to an empty file would begin writing at line 2 instead of 1 due to a reader bug.
BUGFIX
Fixed a bug where the writer would skip writing new keys and values following an empty section.
- Release v0.9.0