#humans make me sad.
#CURL is my lovely gem, a masterpiece they ever created, but what do I see on their documentation pages? This:
CURLcode res = ...
if(!res) {
...
That's how they check for success, meow.
On, no. Meow! Meow! Meow!
And this does not discourage humans to write such posts
daniel.haxx.se/blog/2021/09/27…
where they say common failures are:
1. Skipping the documentation!
2. Failure to check return codes
meow ((((
Common mistakes when using libcurl
I've been traveling this road for a while. Here's my collection of 15 of the most common mistakes and issues people will run into when writing applications and services that use libcurl.daniel.haxx.se
daniel:// stenberg://
in reply to thoughtful_pet • • •thoughtful_pet
in reply to daniel:// stenberg:// • • •daniel:// stenberg://
in reply to thoughtful_pet • • •thoughtful_pet
in reply to daniel:// stenberg:// • • •@bagder pets have much limited mental resources, and they are wasted to translate !res to res == CURLE_OK
At a pet's glance the latter is shouting whereas !res means something is not in the way things should go, need to dig deeper and check what's wrong. With one-day memory retention capabilities it's much harder to memorize that simply means okay