ObjFW  All files named "src/OFStreamObserver_kqueue.m"

This is used instead for time intervals now instead of doubles. file: [5ec1bb5587] check-in: [dc31ce3d34] user: js, branch: trunk, size: 4114 [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: [49f47f6ab0] check-in: [3d16a30f41] user: js, branch: trunk, size: 4030 [annotate] [blame] [check-ins using] [diff]

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

Using an assertion there was not a good idea. file: [9a99bdfa5c] check-in: [e5157b2ba2] user: js, branch: trunk, size: 3997 [annotate] [blame] [check-ins using] [diff]

This is only relevant for platforms on which kqueue uses int for the
number of events instead of size_t. file: [1e1bf29b71] check-in: [19df6b304d] user: js, branch: trunk, size: 3904 [annotate] [blame] [check-ins using] [diff]

As cancel internally was an event, -[observeWithTimeout:] returned YES
before when an observe call was canceled. Now, the number of real events
is counted and NO returned if this is 0. file: [e69a794cf2] check-in: [3de549d6a5] user: js, branch: trunk, size: 3632 [annotate] [blame] [check-ins using] [diff]

This greatly improves performance, as it gets rid of the overhead of
OFAutoreleasePool. file: [ef7d60eaa2] check-in: [1255f3a11a] user: js, branch: trunk, size: 3486 [annotate] [blame] [check-ins using] [diff]

This is to be used when the condition includes a statement that needs to
be executed, as with assert, this would not be executed anymore when
NDEBUG is defined. file: [0f25fb90be] check-in: [417b213d41] user: js, branch: trunk, size: 3515 [annotate] [blame] [check-ins using] [diff]

Also adds more checks. file: [c2387049cc] check-in: [d5ddb2cb48] user: js, branch: trunk, size: 3467 [annotate] [blame] [check-ins using] [diff]

Per convention, this would not be necessasry. However, a common
use case is to call -[observe] in a loop that never ends, thus
no pool below the one created in -[observe] will ever be released. file: [b5282d84cd] check-in: [95fdb174f6] user: js, branch: trunk, size: 3449 [annotate] [blame] [check-ins using] [diff]

This is safe as an "exception loop" can't happen, since if allocating
an exception fails, it throws an OFAllocFailedException which is
preallocated and can always be thrown.

So, the worst case would be that an autorelease of an exception fails,
triggering an OFOutOfMemoryException for which there is no memory,
resulting in an OFAllocFailedException to be thrown. file: [fea66ded56] check-in: [e1e7ffa903] user: js, branch: trunk, size: 3197 [annotate] [blame] [check-ins using] [diff]

EV_RECEIPT is not available on all systems implementing kqueue. file: [24c0cc0a69] check-in: [1edb3cb8c7] user: js, branch: trunk, size: 3185 [annotate] [blame] [check-ins using] [diff]