It is possible to vote on whether to mark a feature as discouraged. C++ didn't invent nullptr to coexist with NULL. If users continue to use old algorithms instead of constrained algorithms year after year, why is the standards committee working on this? linter is also part of the c++ ecosystem, and the committee should respond. C++ has long been plagued by security problems, print is a safe alternative to printf, and continuing to use printf is hastening the death of C++.

________________________________
From: Jonathan Wakely <cxx_at_[hidden]>
Sent: Sunday, November 5, 2023 21:05
To: C++ Proposals <std-proposals_at_[hidden]>
Cc: Yexuan Xiao <bizwen_at_[hidden]>
Subject: Re: [std-proposals] Keeping C++ Young: Migrating to Modern C++



On Sun, 5 Nov 2023, 12:56 Yexuan Xiao via Std-Proposals, <std-proposals_at_[hidden]<mailto:std-proposals_at_[hidden]>> wrote:
Facilities like printf were meaningless after prinf was added to the standard, but since printf is widely used, deprecateing them is harmful to C++. new is vital to C++, we need its placement version, and deprecateing it harms C++'s ability. NULL, rand, qsort that should not continue to be used, but they should not be removed either.


Again, this is something better handled by a linter or code analysis tool.

My project might want to replace all uses of rand() but keep using printf. With a third party tool I can select which suggestions to enable/disable for a given project.