ObjFW  Check-in [0ac7e646b4]

Overview
Comment:README.md: Fix typo
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | 1.1
Files: files | file ages | folders
SHA3-256: 0ac7e646b4f55b80cc40bedfc9b95a208835b77e2ce64667e7043a2a922ebe39
User & Date: js on 2024-08-17 10:11:04
Other Links: branch diff | manifest | tags
Context
2024-08-17
10:48
README.md: Move most of the content to the wiki check-in: 94501f5185 user: js tags: 1.1
10:11
README.md: Fix typo check-in: 0ac7e646b4 user: js tags: 1.1
10:10
README.md: Fix typo check-in: 6d4eb68bdf user: js tags: trunk
2024-08-16
22:13
runtime: Hide symbols for mutex / once / TLS key check-in: ed8107953d user: js tags: 1.1
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Modified README.md from [1d97f3d87c] to [e71051f6a5].

︙︙
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66

  compatible with GCC ≥ 4.6 to allow maximum portability.

  ObjFW is intentionally incompatible with Foundation. This has two reasons:

   * GNUstep already provides a reimplementation of Foundation, which is only
     compatible to a certain degree. This means that a developer still needs to
     care about differences between frameworks if they want to be portable. The
     idea behind ObjFW is that a developer does not need to concern themselves
     with portability and making sure their code works with multiple
     frameworks: Instead, if it works it ObjFW on one platform, they can
     reasonably expect it to also work with ObjFW on another platform. ObjFW
     behaving differently on different operating systems (unless inevitable
     because it is a platform-specific part, like the Windows Registry) is
     considered a bug and will be fixed.
   * Foundation predates a lot of modern Objective-C concepts. The most
     prominent one is exceptions, which are only used in Foundation as a
     replacement for `abort()`. This results in cumbersome error handling,








|

|








50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66

  compatible with GCC ≥ 4.6 to allow maximum portability.

  ObjFW is intentionally incompatible with Foundation. This has two reasons:

   * GNUstep already provides a reimplementation of Foundation, which is only
     compatible to a certain degree. This means that a developer still needs to
     care about differences between frameworks if they want to be portable. The
     idea behind ObjFW is that developers do not need to concern themselves
     with portability and making sure their code works with multiple
     frameworks: Instead, if it works with ObjFW on one platform, they can
     reasonably expect it to also work with ObjFW on another platform. ObjFW
     behaving differently on different operating systems (unless inevitable
     because it is a platform-specific part, like the Windows Registry) is
     considered a bug and will be fixed.
   * Foundation predates a lot of modern Objective-C concepts. The most
     prominent one is exceptions, which are only used in Foundation as a
     replacement for `abort()`. This results in cumbersome error handling,
︙︙