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.
Reducing/removing sscanf use
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Daniel Stenberg via curl-library <curl-library_at_lists.haxx.se>
Date: Fri, 6 Dec 2024 09:13:05 +0100 (CET)
Hi,
Generally, I believe using sscanf() for string parsing is a footgun so I have
over a long time been working on reducing sscanf calls in curl.
Now there is a graph showing this progress:
https://curl.se/dashboard1.html#sscanf
There is also this PR that can remove the last three sscanf() calls
completely, by also introducing a set of string parsing functions:
https://github.com/curl/curl/pull/15692
When that is done, we can ban sscanf completely from being used to not
accidentaly re-introduce any:
https://github.com/curl/curl/pull/15687
Date: Fri, 6 Dec 2024 09:13:05 +0100 (CET)
Hi,
Generally, I believe using sscanf() for string parsing is a footgun so I have
over a long time been working on reducing sscanf calls in curl.
Now there is a graph showing this progress:
https://curl.se/dashboard1.html#sscanf
There is also this PR that can remove the last three sscanf() calls
completely, by also introducing a set of string parsing functions:
https://github.com/curl/curl/pull/15692
When that is done, we can ban sscanf completely from being used to not
accidentaly re-introduce any:
https://github.com/curl/curl/pull/15687
-- / daniel.haxx.se || https://rock-solid.curl.dev -- Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.htmlReceived on 2024-12-06