Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

curl_mprintf.3: add description #7010

Closed
wants to merge 1 commit into from
Closed

curl_mprintf.3: add description #7010

wants to merge 1 commit into from

Conversation

bagder
Copy link
Member

@bagder bagder commented May 5, 2021

These functions have existed in the API since the dawn of time. It is
about time we describe how they work, even if we discourage users from
using them.

These functions have existed in the API since the dawn of time. It is
about time we describe how they work, even if we discourage users from
using them.

See this table for notable exceptions.
.RS
We discourage users from using any of these functions in new applications.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think deprecated might be a better term as it is more common among various APIs

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

deprecated implies it's going to be removed

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Leads to the same goal though

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm avoiding the use of word deprecated since it might give the impression that the function is going away in a foreseeable time. Some years ago I think we even anticipated that future, but these days I think we're more of the mindset that we will never remove any functions from the API (for all practical senses of the word, like decades).

I still want to discourage users from using the *mprintf() functions since they're not as complete and standards compliant like most modern *printf() implementations and it saves both users and us from problems if they rather lean on those than on our implementations.

@bagder bagder closed this in e2497c7 May 6, 2021
@bagder bagder deleted the bagder/docs-mprintf branch July 30, 2021 14:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

3 participants