ObjFW  History of src/OFStdIOStream.h of dd49efb579887489

All necessary changes to adjust for the changes made in trunk are
included in the merge commit. file: [4b04bb450d] check-in: [3c88df0ce4] user: js, branch: amiga-library, size: 4677 [annotate] [blame] [check-ins using] [diff]

This is done by using functions that return a reference to the variable
and defining of_std{in,out,err} to a call into these functions. file: [30b6ddea45] check-in: [9697334084] user: js, branch: amiga-library, size: 4797 [annotate] [blame] [check-ins using] [diff]

This is required for the Amiga library. file: [22e16b8a6e] check-in: [343501981b] user: js, branch: amiga-library, size: 4465 [annotate] [blame] [check-ins using] [diff]

This has been fixed upstream in amiga-gcc. file: [71e9d3c2a0] check-in: [b31bd48f90] user: js, branch: trunk, size: 2180 [annotate] [blame] [check-ins using] [diff]

The reason for this is that, in theory, this also supports versions
older than 3. file: [62b2bfde7a] check-in: [5831626f68] user: js, branch: trunk, size: 2303 [annotate] [blame] [check-ins using] [diff]

As we define the ABI, we can just replace BOOL with bool everywhere,
including in ObjFW itself. For the Apple platforms where BOOL and bool
are different, this is not a problem as BOOL and bool are passed and
returned the same way in the ABI.

This still defines BOOL to bool for compatibility, except on AmigaOS and
Wii, which both have its own BOOL type. file: [230fa44006] check-in: [fe2cbe0021] user: js, branch: trunk, size: 2180 [annotate] [blame] [check-ins using] [diff]

Instead of letting OFStream conform to it, which itself does not really
conform to it, let all the subclasses that actually do conform to it. file: [9c739b6c2b] check-in: [69749b6a5b] user: js, branch: trunk, size: 2194 [annotate] [blame] [check-ins using] [diff]

This improves Swift compatibility. file: [32be342324] check-in: [f3ccf14461] user: js, branch: trunk, size: 2024 [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: [4a5715f270] check-in: [2f4e0df8be] user: js, branch: trunk, size: 2124 [annotate] [blame] [check-ins using] [diff]

This reduces the ifdef hell and makes much more sense, as with ixemul,
no native calls are allowed. file: [791f773daf] check-in: [c9621825fc] user: js, branch: trunk, size: 2110 [annotate] [blame] [check-ins using] [diff]

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

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

The previous way was to set the codepage to UTF-8, however, this does
not work properly on some versions of Windows.

Instead, this catches reads / writes on of_std* on the lowlevel,
interprets it as UTF-8, converts it to / from UTF-16 and then uses
ReadConsoleW() / WriteConsoleW().

Surrogates being cut in the middle is not properly handled yet, this
will be implemented in a follow up commit. file: [70525b9be4] check-in: [3e1b6bccbc] user: js, branch: trunk, size: 1497 [annotate] [blame] [check-ins using] [diff]

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

While at it, also update the mail address. file: [f1e2e1ce28] check-in: [2a27cf3000] user: js, branch: trunk, size: 1451 [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: [eb19e9f509] check-in: [d526d938d7] user: js, branch: trunk, size: 1447 [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: [75654b8c7a] check-in: [b7097a67b6] user: js, branch: trunk, size: 1427 [annotate] [blame] [check-ins using] [diff]

This is used for of_std{in,out,err} now instead of OFFile. file: [a177a89d97] check-in: [085bfc12a0] user: js, branch: trunk, size: 1170 [annotate] [blame] [check-ins using]