ObjFW  History of src/OFDictionary.h of 4bb1e7096e1c61ea

While the idea sounds nice that the tag name is the class, this means the
serialization includes whether something is mutable or immutable. This means
doing as much as making something immutable changes the serialization, which
can then cause issues after being deserialized. file: [b2fad599b6] check-in: [6ce0093f8d] user: js, branch: trunk, size: 9646 [annotate] [blame] [check-ins using] [diff]

It duplicates the functionality of -[OFMutableURI setQueryDictionary:]. file: [73af2a9ef3] check-in: [f1bf64ca9f] user: js, branch: trunk, size: 9691 [annotate] [blame] [check-ins using] [diff]

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

This allows ABI stability with the fragile ABI. file: [0bdd64401a] check-in: [496695d778] user: js, branch: trunk, size: 9369 [annotate] [blame] [check-ins using] [diff]

This improves Swift compatibility. file: [d4aab8a73d] check-in: [f3ccf14461] user: js, branch: trunk, size: 9383 [annotate] [blame] [check-ins using] [diff]

Instead, explicitly declare them, as OF_ASSUME_NONNULL_{BEGIN,END} does
not apply to implicit return types. This means that after this commit,
all init methods have a nonnull return type, as they should have. file: [72d79ae93c] check-in: [2f4e0df8be] user: js, branch: trunk, size: 9487 [annotate] [blame] [check-ins using] [diff]

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

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

If this is only overridden in OFMutableDictionary, this would lead to
inconsistent behavior, as it could be called on an OFDictionary as well
due to the fact that -[setValue:forKey:] is defined in OFObject.
Instead, if the dictionary is immutable, an OFUndefinedKeyException is
thrown. file: [dff64e5368] check-in: [f816d1ec7c] user: js, branch: trunk, size: 9203 [annotate] [blame] [check-ins using] [diff]

If the key starts with an @, the @ is stripped and the super method is
called. Otherwise, this is equivalent to -[objectForKey:] /
-[setValue:forKey:]. file: [2d197e0288] check-in: [cbacea7ca3] user: js, branch: trunk, size: 8735 [annotate] [blame] [check-ins using] [diff]

While at it, also update the mail address. file: [3657eb7ffb] check-in: [cec0f072f8] user: js, branch: 0.8, size: 8291 [annotate] [blame] [check-ins using] [diff]

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

Now that Clang switched to use _Nullable and _Nonnull instead of
__nullable / __nonnull, there is no longer a conflict with glibc, which
means we can just define _Nullable / _Nonnull to nothing if they are not
understood by the compiler (which did not work with __nullable /
__nonnull due to this conflict).

This also defines _Null_unspecified to nothing if unavailable. file: [77b3d41c42] check-in: [d526d938d7] user: js, branch: trunk, size: 8269 [annotate] [blame] [check-ins using] [diff]

Using __nonnull directly doesn't work on systems using glibc, as glibc
defines __nonnull as a parameterized define. While this does not fix the
problem of Clang introducing __nonnull even though it conflicts with
glibc, this at least means it's possible again to compile things with
versions of Clang that don't support __nonnull on systems with glibc. file: [66a93812a2] check-in: [b7097a67b6] user: js, branch: trunk, size: 8287 [annotate] [blame] [check-ins using] [diff]

@compatibility_alias breaks when enabling the new Clang module support. file: [22fec78e10] check-in: [ac1ae59c91] user: js, branch: trunk, size: 6906 [annotate] [blame] [check-ins using] [diff]

No support for extensions yet.

This obsoletes BinaryPack. file: [b0916ad208] check-in: [cba771824e] user: js, branch: trunk, size: 6850 [annotate] [blame] [check-ins using] [diff]

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

It is still implemented by all classes implementing OFCollection so far,
but new classes are not required to implement it anymore.

This is required to add OFCountedSet later, which can't support it. file: [8a0c697234] check-in: [8ff55bf218] user: js, branch: trunk, size: 6283 [annotate] [blame] [check-ins using] [diff]

We assume now that every object understands retain, release, etc. so
that we can weaken the type from OFObject* to id. This makes it
possible to use different root object classes. file: [63820ae3f4] check-in: [e2b06423e0] user: js, branch: trunk, size: 4702 [annotate] [blame] [check-ins using] [diff]

ivars are now named like this: thisIsAnIVar. If an accessor exists for
the ivar, the ivar is named like the accessor. This is required for
@property to work. file: [56783e6894] check-in: [37db8f0fb3] user: js, branch: trunk, size: 4193 [annotate] [blame] [check-ins using] [diff]

The new implementation is easier to use as it does automatic resizing,
but therefore it's not realtime-capable anymore. The new implementation
should also be a little bit faster.

I decided to change the implementation as only very few need a
realtime-capable dictionary and those few will most likely write their
own implementation for their specific case anyway.

As the new implementation no longer uses OFList, this also made it
possible to remove a hack from OFList. file: [27b0d8980d] check-in: [bbf1f79b8f] user: js, branch: trunk, size: 3450 [annotate] [blame] [check-ins using] [diff]

OFDictionary:
* More optimized way to internally store the data.
* Faster resizing of dictionaries (no rehashing anymore).

OFIterator:
* Return a key/object pair rather than first the key and then the
object.

OFList:
* Support for list objects with a different size so you can have your
own list object structs. file: [8038342f92] check-in: [24ecf55297] user: js, branch: trunk, size: 3812 [annotate] [blame] [check-ins using] [diff]

OFArray:
* Rename - object: to - objectAtIndex:.

OFDataArray:
* Rename - item: to - itemAtIndex:.

OFDictionary:
* Rename - get: to - objectForKey:.
* Rename - set:to: to - setObject:forKey:.
* Rename - remove: to - removeObjectForKey:. file: [12bb9cf14f] check-in: [a29d403286] user: js, branch: trunk, size: 3915 [annotate] [blame] [check-ins using] [diff]

When using OFObject*, you have to cast to get rid of a warning when
calling methods on the returned object. file: [7c028d029d] check-in: [9338313079] user: js, branch: trunk, size: 2010 [annotate] [blame] [check-ins using] [diff]