ObjFW  History of src/OFString+JSONParsing.m of 6fbc3b18c717dc97

This uses the same format as OFEnsure(). file: [4b9a43cc0d] check-in: [c86b8f10f0] user: js, branch: trunk, size: 13079 [annotate] [blame] [check-ins using] [diff]

This is only migrating some places, others will be migrated as they are
touched. file: [0ac530152e] check-in: [a0fd103a0b] user: js, branch: trunk, size: 13049 [annotate] [blame] [check-ins using] [diff]

The new names should be more accurate. file: [57caefd874] check-in: [627511b032] user: js, branch: trunk, size: 13089 [annotate] [blame] [check-ins using] [diff]

-[allocMemoryWithSize:] has book keeping overhead that is unnecessary
for temporary memory. file: [c0346b7fe9] check-in: [0ddaac3f5b] user: js, branch: trunk, size: 13091 [annotate] [blame] [check-ins using] [diff]

While it makes sense to wrap malloc and calloc to replace the error
checking with exceptions, it does not make sense to wrap free. file: [6d4d4d10b0] check-in: [3d8286feee] user: js, branch: trunk, size: 13091 [annotate] [blame] [check-ins using] [diff]

This solves the old signed vs. unsigned problem and allows for more
bases than just 8, 10 and 16, as well as auto-detection of the base (if
base is 0). file: [2f361d6379] check-in: [b6ee372b98] user: js, branch: trunk, size: 13084 [annotate] [blame] [check-ins using] [diff]

There is no reliable way to check if C++ already defined those, as Clang
now defines char{16,32}_t even when it is not in C++ 11 mode. So we
cannot check if we are not in C++ 11 and then define them and otherwise
rely on the C++ 11 types. file: [0d9de1d0b0] check-in: [505137f25f] user: js, branch: trunk, size: 12995 [annotate] [blame] [check-ins using] [diff]

Casts are now written like types in variable declarations. file: [44a7ffa4d7] check-in: [4af49a13c3] user: js, branch: trunk, size: 13019 [annotate] [blame] [check-ins using] [diff]

Forgot to add 2017, even though I already did quite some changes in
2017. file: [3ded34b885] check-in: [44f45c2e35] user: js, branch: trunk, size: 13014 [annotate] [blame] [check-ins using] [diff]

It makes no sense here. file: [eaa788e234] check-in: [1e9a23441b] user: js, branch: trunk, size: 13008 [annotate] [blame] [check-ins using] [diff]

While at it, also update the mail address. file: [77e12ed016] check-in: [2a27cf3000] user: js, branch: trunk, size: 13188 [annotate] [blame] [check-ins using] [diff]

Those were only a problem if the user created its own OFString subclass,
as calls to -[UTF8String] could then create a new, autoreleased C
string. As OFString_UTF8 simply returns the internal C string, this
hasn't been a problem when not subclassing OFString. file: [2d16a6d32f] check-in: [b5c8b62533] user: js, branch: trunk, size: 13178 [annotate] [blame] [check-ins using] [diff]

This means that OFObject.h imports macros.h now, making it unnecessary
to manually import macros.h in almost every file. And while at it, also
import autorelease.h in OFObject.h, so that this doesn't need to be
manually imported in almost every file as well. file: [f9c7af6229] check-in: [13ee56edf3] user: js, branch: trunk, size: 13070 [annotate] [blame] [check-ins using] [diff]

No functional change intended. file: [848285d233] check-in: [9da9b2b64c] user: js, branch: trunk, size: 13090 [annotate] [blame] [check-ins using] [diff]

This mostly removes the argument for the class in which the exception
occurred. As backtraces were recently added for all platforms, the
passed class does not give any extra information on where the exception
occurred anymore.

This also removes a few other arguments which were not too helpful. In
the past, the idea was to pass as many arguments as possible so that it
is easier to find the origin of the exception. However, as backtraces
are a much better way to find the origin, those are not useful anymore
and just make the exception more cumbersome to use. The rule is now to
only pass arguments that might help in recovering from the exception or
provide information that is otherwise not easily accessible. file: [c7c766a996] check-in: [3d16a30f41] user: js, branch: trunk, size: 13069 [annotate] [blame] [check-ins using] [diff]

The only places where BOOL is left are those where they are required by
the ABI. file: [b110ce39ff] check-in: [c5ef582958] user: js, branch: trunk, size: 13063 [annotate] [blame] [check-ins using] [diff]

This adds support for Infinity and leading + signs. file: [534d095364] check-in: [f59977a0aa] user: js, branch: trunk, size: 13019 [annotate] [blame] [check-ins using] [diff]

The default is 32. file: [9c5a92bb7c] check-in: [d60c3ae1ec] user: js, branch: trunk, size: 12784 [annotate] [blame] [check-ins using] [diff]

This introduces OFInvalidJSONException, which has a property line to get
the line in which the parsing error occurred. file: [291a080964] check-in: [72c71c4eb2] user: js, branch: trunk, size: 12343 [annotate] [blame] [check-ins using] [diff]

This completes the JSON5 support. file: [e03da095af] check-in: [c9a3ac1a03] user: js, branch: trunk, size: 11553 [annotate] [blame] [check-ins using] [diff]

Supported so far:
* comments
* single quoted strings file: [8ad19cb41d] check-in: [54f80aba7a] user: js, branch: trunk, size: 8658 [annotate] [blame] [check-ins using] [diff]

This allows modifying data and getting the JSON representation again. file: [887f63d0ca] check-in: [acd8e03f58] user: js, branch: trunk, size: 8626 [annotate] [blame] [check-ins using] [diff]

While comments are not part of the JSON standard itself, allowing them
makes JSON a useful format for configurations and accepting more than is
required never hurts. file: [12e5560901] check-in: [6203c9e8f2] user: js, branch: trunk, size: 8661 [annotate] [blame] [check-ins using] [diff]