ObjFW  History of src/OFNumber.h of a77bb2825d153326

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: [bb1eda01eb] check-in: [6ce0093f8d] user: js, branch: trunk, size: 10281 [annotate] [blame] [check-ins using] [diff]

GCC now supports the attribute, but still complains if the method is not
implemented, so always implement it with a method that throws. file: [eff21822aa] check-in: [e53c0160a8] user: js, branch: trunk, size: 10326 [annotate] [blame] [check-ins using] [diff]

These methods no longer exist. file: [4b9e5cee54] check-in: [27002f2efe] user: js, branch: trunk, size: 10456 [annotate] [blame] [check-ins using] [diff]

This is a requirement for tagged pointer numbers, which cannot have
ivars. file: [ff0ae5f35c] check-in: [bc9998913a] user: js, branch: tagged-pointers, size: 10761 [annotate] [blame] [check-ins using] [diff]

Since C guarantees minimum sizes for char, short, int, long and long
long, these can be used instead. file: [5740ff4672] check-in: [25c985fec1] user: js, branch: trunk, size: 10873 [annotate] [blame] [check-ins using] [diff]

It's a non-standard type that should only be used for matching POSIX
APIs. file: [833a3447d8] check-in: [be8b442546] user: js, branch: trunk, size: 17942 [annotate] [blame] [check-ins using] [diff]

It is not guaranteed that a type encoding for it exists. file: [66f566bece] check-in: [d74f244ab7] user: js, branch: trunk, size: 18527 [annotate] [blame] [check-ins using] [diff]

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

This improves Swift compatibility. file: [0a882a919b] check-in: [f3ccf14461] user: js, branch: trunk, size: 20508 [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: [92dadecb01] check-in: [2f4e0df8be] user: js, branch: trunk, size: 21303 [annotate] [blame] [check-ins using] [diff]

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

While this makes moving things around easier, this has been done by
accident and looks ugly. file: [1972eca1cd] check-in: [3572e824c6] user: js, branch: trunk, size: 20763 [annotate] [blame] [check-ins using] [diff]

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

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

This increases the required GCC version from 4.0 to 4.6 (exception:
Apple GCC, which already supports this with >= 4.0 starting with OS X
10.5). Since even GCC 4.6 is really old by now, there is no point in
still supporting something even older and making the code ugly because
of that. While some hardware and OS support was dropped from GCC 4.6
compared to GCC 4.0, there is nothing in there that would be an
interesting target with the exception of BeOS maybe - but a port to BeOS
can also be achieved using the Haiku support. The other dropped OSes are
mostly old versions of OSes while newer ones are still being supported
(and those newer versions of those OSes still support the same
hardware). file: [d5e0f4a58d] check-in: [48980f2297] user: js, branch: trunk, size: 20760 [annotate] [blame] [check-ins using] [diff]

These methods encouraged doing arithmetic on objects rather than getting
the C type value, doing the arithmetic and creating a new object. They
didn't do anything else internally, and so doing this manually isn't
slower - it's even faster if you do multiple operations, as no temporary
objects are created then.

Another advantage of this is that there are no longer uncertainties
about types of different OFNumber objects when doing arithmetic, as the
user has to be explicit about the types when getting the C type value
and thus knows which types will be used for the arithmetic. file: [25b9edab19] check-in: [366681bebe] user: js, branch: trunk, size: 20849 [annotate] [blame] [check-ins using] [diff]

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

No support for extensions yet.

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

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

This solves problems on systems where __block is used in unistd.h. file: [0944a92f2e] check-in: [368fffb61e] user: js, branch: 0.5, size: 16030 [annotate] [blame] [check-ins using] [diff]

This solves problems on systems where __block is used in unistd.h. file: [6c0dda2992] check-in: [eced1d58ea] user: js, branch: trunk, size: 20194 [annotate] [blame] [check-ins using] [diff]