ObjFW  History of src/OFApplication.h of b829f3e79860ea27

It is unclear whether the same API can be applied to other sandboxing
frameworks. file: [090cdb1ff6] check-in: [510628432f] user: js, branch: 1.0, size: 8192 [annotate] [blame] [check-ins using] [diff]

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

While the active sandbox can be changed, a different sandbox must not be
activated. The reason for this is that allowing to activate a different
sandbox makes it impossible to track which paths have already been
unveiled. file: [2092ccca9e] check-in: [e0c2e70f7b] user: js, branch: trunk, size: 9653 [annotate] [blame] [check-ins using] [diff]

This is done at compile time now rather than at runtime. file: [b0172a54c9] check-in: [54b38752bb] user: js, branch: trunk, size: 7418 [annotate] [blame] [check-ins using] [diff]

This improves Swift compatibility. file: [8d82cea2e5] check-in: [a2e849c681] user: js, branch: trunk, size: 7479 [annotate] [blame] [check-ins using] [diff]

This improves Swift compatibility. file: [5c5c92ace5] check-in: [f3ccf14461] user: js, branch: trunk, size: 7069 [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: [45023093c6] check-in: [2f4e0df8be] user: js, branch: trunk, size: 7267 [annotate] [blame] [check-ins using] [diff]

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

This changes retaining behavior, meaning properties are not returned
retained and autoreleased anymore, so a property returned from a getter
now needs to be manually retained and autoreleased before calling the
setter. However, this is rarely the case and not using atomic improves
performance. file: [ce51a82a57] check-in: [0a73af49f0] user: js, branch: trunk, size: 7084 [annotate] [blame] [check-ins using] [diff]

Only OpenBSD's pledge() is supported so far. file: [2f26626383] check-in: [40cf53506a] user: js, branch: trunk, size: 7075 [annotate] [blame] [check-ins using] [diff]

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

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

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

Now that we can require GCC >= 4.6, we no longer need to have a category
on OFObject that adds the optional protocol to it. file: [3d009b0fda] check-in: [ba62f00fac] user: js, branch: trunk, size: 6466 [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: [91ca5aaec7] check-in: [48980f2297] user: js, branch: trunk, size: 6581 [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: [5756d4c723] check-in: [d526d938d7] user: js, branch: trunk, size: 7049 [annotate] [blame] [check-ins using] [diff]

This is necessary to make GCC (>= 4.6 and Apple GCC) happy as they don't
like the list of property attributes ending in a comma. file: [ed8ed6f607] check-in: [80e1a9655b] user: js, branch: trunk, size: 7057 [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: [e950676ac5] check-in: [b7097a67b6] user: js, branch: trunk, size: 7046 [annotate] [blame] [check-ins using] [diff]

It causes just too much trouble: It breaks with some old versions of
Clang, where noreturn does not work correctly, and OS X headers break if
noreturn is defined, requiring an ugly and fragile workaround. It's just
not worth the trouble it causes, as the same functionality is available
through __attribute__((__noreturn__)). file: [ce851e8072] check-in: [716b1fc2b3] user: js, branch: trunk, size: 6486 [annotate] [blame] [check-ins using] [diff]

If it's unavailable, it's defined to __attribute__((noreturn)).

Unfortunately, it cannot be used for ObjC methods, as noreturn is part
of the return type while __attribute__((noreturn)) needs to be at the
end for an ObjC method. To make matters worse, even GCC versions that
accept noreturn don't allow it for an ObjC method. Thus, the only thing
that can be done is to always use __attribute__((noreturn)) for ObjC
methods using the OF_METHOD_NORETURN define. file: [4b9b47fc09] check-in: [bac91ccede] user: js, branch: trunk, size: 6510 [annotate] [blame] [check-ins using] [diff]

It still stores the normal argc/argv for compatibility, however, the
argument array is created from the Unicode arguments instead.

This also makes -[OFApplication setArgumentCount:andArgumentValues:]
private. file: [24a84dfbfd] check-in: [fb1f29bd30] user: js, branch: trunk, size: 6275 [annotate] [blame] [check-ins using] [diff]

There is no need to reference count them, they will always be retained
by the application for the lifetime of the application. file: [26fb77f30b] check-in: [9ec315d070] user: js, branch: trunk, size: 4576 [annotate] [blame] [check-ins using] [diff]

This makes it possible to pass argc and argv to third party libs
requiring those. file: [53d78093d3] check-in: [f282aaa672] user: js, branch: trunk, size: 3471 [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: [c960316ed3] check-in: [e2b06423e0] user: js, branch: trunk, size: 3194 [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: [ad7af612fb] check-in: [37db8f0fb3] user: js, branch: trunk, size: 2621 [annotate] [blame] [check-ins using] [diff]