ObjFW  Check-in [5bf1d19ec2]

Overview
Comment:README.md: Fix typo
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | 1.0
Files: files | file ages | folders
SHA3-256: 5bf1d19ec2f8a3008242de4e32b9cbb929c86035094e4388f438ac936aac4a48
User & Date: js on 2023-10-28 20:38:30
Other Links: branch diff | manifest | tags
Context
2023-11-04
14:44
OFAllocObject: Fix calculation of extra alignment check-in: 973574d1bd user: js tags: 1.0
2023-10-28
20:38
README.md: Fix typo check-in: 5bf1d19ec2 user: js tags: 1.0
18:55
README.md: Fix typo check-in: d36ac8babf user: js tags: trunk
2023-10-24
21:13
Use GetModuleHandle where possible check-in: 1f98847350 user: js tags: 1.0
Changes

Modified README.md from [81aa3049f8] to [6e10392554].

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

  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 portablility 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







|







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

  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