ObjFW  Artifact Description [a3fba56a2a]

Artifact a3fba56a2a52feb6649e5334389882e99423f04d45c1b094cc5613d75670a991:

• File extra.mk.in
  • 2022-08-07 20:46:51 — part of check-in [1ad52a2f2c] on branch trunk — Rewrite objfw-new in ObjC

    This offers more flexibility in the future, e.g. to generate classes
    with properties. (user: js, size: 3144) [annotate] [blame] [check-ins using]

  • 2022-10-18 21:34:46 — part of check-in [d1dd66e668] on branch 1.0 — Merge trunk into 1.0 branch (user: js, size: 3144) [annotate] [blame] [check-ins using]
  • 2022-10-30 18:58:13 — part of check-in [0b4f713964] on branch trunk — Remove AppleTalk support again

    It seems that neither Windows nor macOS support DDP sockets, but only
    the layers on top, while neither Linux nor NetBSD support the layers on
    top, but only provide DDP.

    It seems that DDP is not meant to be used directly, while Linux and
    NetBSD only provide the minimum to use netatalk, which is DDP. ObjFW
    would need to use the layers on top on Windows and macOS and implement
    those layers itself on Linux and NetBSD. This also means that no code
    would be shared between Linux / NetBSD and Windows / macOS, as it's
    impossible to have one implementation that works for everything. At this
    point, the effort required doesn't make sense. (user: js, size: 3144) [annotate] [blame] [check-ins using]