ObjFW  History of src/threading_pthread.m of 50a6ffd4b105d33f7970e469eb3e270c93ca4c79c910232fc1f27a99c6023a78

Some systems do not provide the functionality. file: [45235a8a16] check-in: [b5430ac44f] user: js, branch: trunk, size: 6262 [annotate] [blame] [check-ins using] [diff]

This fixes NetBSD 8. file: [b133b4ffce] check-in: [cdd30dfb53] user: js, branch: trunk, size: 6343 [annotate] [blame] [check-ins using] [diff]

The name of the thread may only be set from the thread itself. So the
thread should read the property on start and set its name. file: [7c690c290a] check-in: [1494d3f6f1] user: js, branch: trunk, size: 6150 [annotate] [blame] [check-ins using] [diff]

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

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

The old definition was quite unpredictable and too platform-specific.
The new one defines -1.0 as lowest priority that still schedules, 0.0 as
the normal priority (meaning the same as the main thread) and +1.0 as
the highest priority that still allows getting preempted. file: [22a0bb4722] check-in: [b4023e6bc0] user: js, branch: trunk, size: 5322 [annotate] [blame] [check-ins using] [diff]

This was forgotten when splitting threading.m into multiple files. file: [706256fda3] check-in: [f58ea581f0] user: js, branch: trunk, size: 5222 [annotate] [blame] [check-ins using] [diff]

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

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

When initializing a pthread_attr_t on Solaris and reading the stack size
from it with pthread_attr_getstacksize(), the stack size returned it 0.
However, when calling pthread_attr_setstacksize() with a stack size of
0, the call fails. file: [5e32541977] check-in: [60ebb21fc7] user: js, branch: trunk, size: 5061 [annotate] [blame] [check-ins using] [diff]

OF_NO_RETURN_FUNC is defined when __attribute__((__noreturn__)) is
supported for functions, whereas OF_NO_RETURN is only defined when it is
supported for both functions and methods. file: [7f18dc085f] check-in: [ffb39d1df6] user: js, branch: trunk, size: 5023 [annotate] [blame] [check-ins using] [diff]

This changes the return type to void, as the return type of a thread's
main depends on the threading implementation used. For pthreads, it adds
a wrapper function which returns NULL to avoid problems with bogus
return values. For WinAPI threads, the function is just casted, as bogus
return values don't seem to matter there. file: [967081c426] check-in: [52e02c06ca] user: js, branch: trunk, size: 4486 [annotate] [blame] [check-ins using] [diff]