C++ Logo

std-proposals

Advanced search

Re: [std-proposals] Safety checks at compile time

From: Phil Bouchard <boost_at_[hidden]>
Date: Tue, 14 Feb 2023 16:00:46 -0500
On 2/14/23 15:57, Roberto R via Std-Proposals wrote:

> Microsoft, Google and NSA, are saying that C++ should be deprecated
> because the cyber security issues due to not memory safe code are
> costing millions. Their statements are too bold and simplify too much
> the world, but there is some true.

I 100% agree with you Roberto. People in the committee tend to disregard
important objective facts.

> Best Regards
>
> Roberto
>
> *From:*Chris Ryan <chrisr98008_at_[hidden]>
> *Sent:* Tuesday 14 February 2023 18:45
> *To:* std-proposals_at_[hidden]
> *Cc:* Jason McKesson <jmckesson_at_[hidden]>; roberto.romani_at_[hidden]
> *Subject:* Re: [std-proposals] Safety checks at compile time
>
> Please read:
> https://thenewstack.io/can-c-be-saved-bjarne-stroustrup-on-ensuring-memory-safety <https://thenewstack.io/can-c-be-saved-bjarne-stroustrup-on-ensuring-memory-safety>
>
> Bjarne gave us an introduction last week at the WG21 ISO C++ Standards
> meeting, in Issaquah on these safety profiles. As per ISO policies the
> meeting was not recorded. I am sure that he will give this talk again
> soon where he can present some of these ideas publicly.
>
> These tools are not ready yet. The idea is a good start, but we can not
> tool ourselves out of this. It does not remove any legacy
> compatibility. It only checks that what you are doing now is
> safe(r). Just because C++ has legacy compatibility does not imply that
> you should be using these older mechanisms.
>
> On Tue, Feb 14, 2023 at 9:13 AM Jason McKesson via Std-Proposals
> <std-proposals_at_[hidden] <mailto:std-proposals_at_[hidden]>>
> wrote:
>
> On Tue, Feb 14, 2023 at 12:02 PM Roberto R via Std-Proposals
> <std-proposals_at_[hidden]
> <mailto:std-proposals_at_[hidden]>> wrote:
> >
> > Hi all
> >
> > I guess many of you have read articles about Microsoft, Google
> and NSA saying that it is better to stop to use C++ and use instead
> memory safe languages like Rust or Java.
>
> No, I haven't heard about that. Though I'm not sure what it matters.
>
> > Is it possible to make C++ a memory safe language?
>
> Not without throwing away backwards compatibility and effectively
> turning it into a different language. And since different languages
> already exist, and this would force people to rewrite their code
> anyway, I'm not sure why they would rewrite it in this new C++.
> --
> Std-Proposals mailing list
> Std-Proposals_at_[hidden] <mailto:Std-Proposals_at_[hidden]>
> https://lists.isocpp.org/mailman/listinfo.cgi/std-proposals
> <https://lists.isocpp.org/mailman/listinfo.cgi/std-proposals>
>
>

-- 
Logo <https://www.fornux.com/>  
*Phil Bouchard*  facebook icon
<https://www.linkedin.com/in/phil-bouchard-5723a910/> 
CTO
T: (819) 328-4743
E: phil_at_[hidden]| www.fornux.com <http://www.fornux.com>
8 rue de la Baie| Gatineau (Qc), J8T 3H3 Canada
Banner <https://goglobalawards.org/> Le message ci-dessus, ainsi que les
documents l'accompagnant, sont destinés uniquement aux personnes
identifiées et peuvent contenir des informations privilégiées,
confidentielles ou ne pouvant être divulguées. Si vous avez reçu ce
message par erreur, veuillez le détruire.
This communication (and/or the attachments) is intended for named
recipients only and may contain privileged or confidential information
which is not to be disclosed. If you received this communication by
mistake please destroy all copies.

Received on 2023-02-14 21:00:47