ObjFW  History of src/runtime/runtime.h of 44f45c2e357301ef

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

This is necessary for ObjC++ with GCC, as otherwise, this generates an
error. Since the objc_abi_module struct is private anyway, there is not
much reason to have the argument of that type. file: [35cbcdf16d] check-in: [4e40a57efa] user: js, branch: trunk, size: 7045 [annotate] [blame] [check-ins using] [diff]

For many of those, it's not actually required to declare them dllexport.
Declaring them at all is enough to prevent Clang from using its implicit
declaration that is dllimport. file: [33b194a33a] check-in: [f57765b5c6] user: js, branch: trunk, size: 7057 [annotate] [blame] [check-ins using] [diff]

This was provided by OFObject before, but should actually be provided by
the runtime, as the compiler can generate code calling into it. file: [3f8b6a0471] check-in: [5e267364ae] user: js, branch: trunk, size: 6446 [annotate] [blame] [check-ins using] [diff]

Also moves out some stuff to functions to be reusable by
class_addMethod(). file: [ee48ca9342] check-in: [d4cae4c963] user: js, branch: trunk, size: 6335 [annotate] [blame] [check-ins using] [diff]

While at it, also update the mail address. file: [6046b12ca6] check-in: [2a27cf3000] user: js, branch: trunk, size: 5970 [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: [abe66d7e40] check-in: [b7097a67b6] user: js, branch: trunk, size: 5966 [annotate] [blame] [check-ins using] [diff]

* dtable.m is now the old sparse array, using IMP as type for values and
thus not violating the C standard anymore (functions may not be stored
in void*)
* New sparsearray.m which can work with any size, based on the sparse
array from the fast path of class.m
* Fast path of class.m now uses the new sparsearray.m file: [eb23c8ebea] check-in: [1ebb9eb7b3] user: js, branch: trunk, size: 5960 [annotate] [blame] [check-ins using] [diff]

This was never used and is not part of the Apple runtime either. file: [d678a70fe3] check-in: [7c0fa1fa85] user: js, branch: trunk, size: 5684 [annotate] [blame] [check-ins using] [diff]

It behaves like in the Apple runtime now. file: [0f2d559e1c] check-in: [3cd9d0ad69] user: js, branch: trunk, size: 5731 [annotate] [blame] [check-ins using] [diff]

It matches the Apple API and ABI now and the forwarding handler itself
determines whether it should forward or not.

This moves handling of +[resolve{Class,Instance}Method:] to the runtime
and allows adding new kinds of forwarding without changing the runtime.

Also fixes a potential stack problem in the forwarding for MIPS. file: [86f17c06b0] check-in: [0c332aa2d2] user: js, branch: trunk, size: 5665 [annotate] [blame] [check-ins using] [diff]

The assembly implementations of the lookup and forwarding still need to
be adjusted. Those just alias to the non-stret version for now so that
linking works, meaning the behaviour is still the same as without
support for objc_msg_lookup_stret for now. file: [8b0a6c7397] check-in: [9713ad857d] user: js, branch: trunk, size: 5296 [annotate] [blame] [check-ins using] [diff]

Also includes a few style improvements for runtime.h. file: [d76a124e2f] check-in: [26f6bd3396] user: js, branch: trunk, size: 5137 [annotate] [blame] [check-ins using] [diff]

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

This makes it easier to use runtime functions in portable code. file: [d874182359] check-in: [120caad331] user: js, branch: trunk, size: 5637 [annotate] [blame] [check-ins using] [diff]

Also adds a missing OF_RETURNS_INNER_POINTER. file: [47cf79266e] check-in: [0b32d65e0c] user: js, branch: trunk, size: 5394 [annotate] [blame] [check-ins using] [diff]

This uses the runtime's autorelease pools and implements autorelease
pools in the ObjFW runtime. It therefore uses ObjFW's autorelease pools
when using the ObjFW runtime and Apple's autorelease pools when using
the Apple runtime.

These new pools should be ARC-compatible now and finally, it should be
possible to mix OFAutoreleasePools and NSAutoreleasePools again, even
@autoreleasepool is allowed in the mix now. This also means the old
bridge to NSAutoreleasePool should not be required anymore, as both use
the runtime's autorelease pools now.

As a bonus, it's significantly faster to use the ObjFW runtime with
ObjFW's autorelease pools than to use Apple's runtime with Apple's
autorelease pools, as a quick benchmark using OFXMLParser on large files
showed. (Note: This is not only due to the different autorelease pools,
but also due to the fact that even with the same autorelease pools it is
faster using the ObjFW runtime, as can be seen in versions prior to this
commit.) file: [10b66bd071] check-in: [f5927f8a84] user: js, branch: trunk, size: 3978 [annotate] [blame] [check-ins using] [diff]

Messaging protocols is deprecated and unreliable. Thus we shouldn't do
it in the runtime either. file: [a7ea76e777] check-in: [df24f80ab0] user: js, branch: runtime, size: 3094 [annotate] [blame] [check-ins using] [diff]