curl / Mailing Lists / curl-library / Single Mail
Buy commercial curl support. We help you work out your issues, debug your libcurl applications, use the API, port to new platforms, add new features and more. With a team lead by the curl founder Daniel himself.

Re: New iOS/macOS Objective-C and Swift wrapper libs

From: Benjamin Erhart via curl-library <curl-library_at_lists.haxx.se>
Date: Fri, 15 Nov 2024 12:10:59 +0100

Am 14.11.24 um 19:36 schrieb Dan Fandrich via curl-library:
> On Thu, Nov 14, 2024 at 01:40:28PM +0100, Benjamin Erhart via curl-library wrote:
>> Just mailing you to let you know I started a new effort to bring libcurl to Apple platforms:
>>
>> 1. piece:
>>
>> https://github.com/greatfire/curl-apple
>
> I've added this one to the downloads page.

Niiice! Thank you!

>> https://github.com/greatfire/SwiftyCurl
>
> This sounds like it belongs on https://curl.se/libcurl/bindings.html as a
> language binding, but I'm not familiar enough with Swift to say whether it
> belongs under the Swift or Objective-C category, since both are mentioned in
> the project.

Oh, yeah, definitely on the bindings page.


I see 3 categories, where it should be mentioned:

- Cocoa
- Objective-C
- Swift


- Cocoa, because there's already somewhat outdated libs mentioned there.
(Which I didn't find in the first place, because "Cocoa" as a category
feels a little off. I was kinda relieved when I noticed that the stuff
mentioned is pretty old, anyways... ;-) )

- Objective-C, because the library is written in Objective-C, hence it
is easy to use with your own Objective-C code.

- Swift, because on Apple platforms, Objective-C and Swift have strong
interoperability. Bindings between them are automatically generated. And
Swift was also my main target to use it with, hence the name.


> Also, the project site talks about "libcurl's own "multi" multithreading",
> except libcurl's multi API has nothing to do with multithreading; it provides
> an alternative to multithreading and, in fact, each handle MUST be used in a
> single thread. It's really an async API that could be considered a way to
> implement cooperative multitasking.

Ahhh. Thanks for that explanation!

I'll adapt this text.


Cheers,

~tla
-- 
Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library
Etiquette:   https://curl.se/mail/etiquette.html
Received on 2024-11-15