ObjFW  History of src/exceptions/OFMoveItemFailedException.m of 3f9e0e0f0717f7eb

Also refactor OFFileManager to make use of them. file: [b4c69e61e3] check-in: [c8defc67ad] user: js, branch: trunk, size: 1766 [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: [265677a4a5] check-in: [2f4e0df8be] user: js, branch: trunk, size: 1791 [annotate] [blame] [check-ins using] [diff]

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

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

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

While at it, also update the mail address. file: [344bb18cd9] check-in: [2a27cf3000] user: js, branch: trunk, size: 1695 [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: [cc6ebc8aa3] check-in: [48980f2297] user: js, branch: trunk, size: 1691 [annotate] [blame] [check-ins using] [diff]

errNo could never be 0 for those exceptions, so there's no point in
returning a different description if errNo is 0. file: [aa0688f8e1] check-in: [e8bb29e8e8] user: js, branch: trunk, size: 1750 [annotate] [blame] [check-ins using] [diff]

The old behaviour where the exception would access errno directly on
creation of the exception was very fragile. The two main problems with
it were that sometimes it would pick up an errno even though none had
been set and in other cases that when the exception was created errno
had already been overridden.

This also greatly increases errno handling on Win32, especially in
conjunction with sockets. It can still be improved further, though. file: [9aecf924e2] check-in: [62e2de30b9] user: js, branch: trunk, size: 1900 [annotate] [blame] [check-ins using] [diff]

This means that OFObject.h imports macros.h now, making it unnecessary
to manually import macros.h in almost every file. And while at it, also
import autorelease.h in OFObject.h, so that this doesn't need to be
manually imported in almost every file as well. file: [2e3b735bfd] check-in: [13ee56edf3] user: js, branch: trunk, size: 1691 [annotate] [blame] [check-ins using] [diff]

This replaces +[OFFile renameItemAtPath:toPath:] and supports moving
files to different logical devices. file: [e630c0adf7] check-in: [260391fc1c] user: js, branch: trunk, size: 1704 [annotate] [blame] [check-ins using]