I posted "writing C for #curl" just a short while ago, which is relevant to the recent "C mistake" graphs.
daniel.haxx.se/blog/2025/04/07…
Writing C for curl
It is a somewhat common question to me: how do we write C in curl to make it safe and secure for billions of installations? Some precautions we take and decisions we make. There is no silver bullet, just guidelines.daniel.haxx.se
Otte Homan - remember Geordie
in reply to daniel:// stenberg:// • • •daniel:// stenberg://
in reply to Otte Homan - remember Geordie • • •Otte Homan - remember Geordie
in reply to daniel:// stenberg:// • • •daniel:// stenberg://
in reply to Otte Homan - remember Geordie • • •Otte Homan - remember Geordie
in reply to daniel:// stenberg:// • • •daniel:// stenberg://
in reply to Otte Homan - remember Geordie • • •Otte Homan - remember Geordie
in reply to daniel:// stenberg:// • • •daniel:// stenberg://
in reply to Otte Homan - remember Geordie • • •Otte Homan - remember Geordie
in reply to daniel:// stenberg:// • • •unixbhaskar
in reply to daniel:// stenberg:// • • •Göran Roseen
in reply to daniel:// stenberg:// • • •daniel:// stenberg://
in reply to Göran Roseen • • •@roseen their internal APIs are at least documented!
github.com/curl/curl/blob/mast…
github.com/curl/curl/blob/mast…
curl/docs/internals/DYNBUF.md at master · curl/curl
GitHubGöran Roseen
in reply to daniel:// stenberg:// • • •