Date: Tue, 14 Feb 2023 21:39:38 -0500
Once C adopts deterministic exception handling, one could just dust off
their copy of CFRONT. Since C doesn't have temporaries scoped to the full
expression, C++ would automatically become significantly memory safer from
dangling of the stack. It'll even reduce the gap between C and C++ which is
appealing to some. About the only thing I would miss is move constructors,
perfect forwarding and guaranteed return value optimization. A small price
to pay for the massive reduction in dangling.
On Tue, Feb 14, 2023 at 7:50 PM Phil Bouchard via Std-Proposals <
std-proposals_at_[hidden]> wrote:
>
>
> On 2/14/23 19:40, Alexander Don wrote:
> > Hi,
> >
> > Standard library offers implementation of a smart pointer.
> > https://en.cppreference.com/book/intro/smart_pointers
> > <https://en.cppreference.com/book/intro/smart_pointers>
> >
> > You would need to redefine existing pointers.
> > C++ may use legacy memory allocation such as Malloc. Sometimes you need
> > this syntax to access memory outside of virtual memory space of the
> > application. Good example would be working with CUDA or low-level driver.
> >
> > Microsoft pushes for their .net standard, and Google have their own
> > libraries and languages.
> >
> > If you already have memory leak issue, use a memory profiling tool.
> > Microsoft's diagnostic tools or vtune are good.
>
> Thanks but getting this fixed implicitly is better.
>
> >
> > Get Outlook for iOS <https://aka.ms/o0ukef>
> > ------------------------------------------------------------------------
> > *From:* Std-Proposals <std-proposals-bounces_at_[hidden]> on
> behalf
> > of Phil Bouchard via Std-Proposals <std-proposals_at_[hidden]>
> > *Sent:* Tuesday, February 14, 2023 4:11:39 PM
> > *To:* std-proposals_at_[hidden] <std-proposals_at_[hidden]>
> > *Cc:* Phil Bouchard <boost_at_[hidden]>
> > *Subject:* Re: [std-proposals] Safety checks at compile time
> >
> >
> > On 2/14/23 18:14, Bjorn Reese via Std-Proposals wrote:
> >> On 2/14/23 18:02, Roberto R via Std-Proposals wrote:
> >>
> >>> Is it possible to make C++ a memory safe language? For sure it is
> >>> possible to make it safer, at least for new code that does not use
> >>> legacy code.
> >>
> >> There is a lot of experimentation going on:
> >>
> >> https://github.com/carbon-language/carbon-lang
> > <https://github.com/carbon-language/carbon-lang>
> >
> > This is exactly what I was looking for actually. Instead of revamping
> > C++, let's properly design a new language inheriting from C++.
> >
> >> https://www.val-lang.dev/ <https://www.val-lang.dev/>
> >>
> >
> > --
> > Logo <https://www.fornux.com/ <https://www.fornux.com/>>
> > *Phil Bouchard* facebook icon
> > <https://www.linkedin.com/in/phil-bouchard-5723a910/
> > <https://www.linkedin.com/in/phil-bouchard-5723a910/>>
> > CTO
> > T: (819) 328-4743
> > E: phil_at_[hidden]| www.fornux.com <http://www.fornux.com>
> > <http://www.fornux.com <http://www.fornux.com>>
> > 8 rue de la Baie| Gatineau (Qc), J8T 3H3 Canada
> >
> > Banner <https://goglobalawards.org/ <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.
> >
> > --
> > Std-Proposals mailing list
> > 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.
>
> --
> Std-Proposals mailing list
> Std-Proposals_at_[hidden]
> https://lists.isocpp.org/mailman/listinfo.cgi/std-proposals
>
their copy of CFRONT. Since C doesn't have temporaries scoped to the full
expression, C++ would automatically become significantly memory safer from
dangling of the stack. It'll even reduce the gap between C and C++ which is
appealing to some. About the only thing I would miss is move constructors,
perfect forwarding and guaranteed return value optimization. A small price
to pay for the massive reduction in dangling.
On Tue, Feb 14, 2023 at 7:50 PM Phil Bouchard via Std-Proposals <
std-proposals_at_[hidden]> wrote:
>
>
> On 2/14/23 19:40, Alexander Don wrote:
> > Hi,
> >
> > Standard library offers implementation of a smart pointer.
> > https://en.cppreference.com/book/intro/smart_pointers
> > <https://en.cppreference.com/book/intro/smart_pointers>
> >
> > You would need to redefine existing pointers.
> > C++ may use legacy memory allocation such as Malloc. Sometimes you need
> > this syntax to access memory outside of virtual memory space of the
> > application. Good example would be working with CUDA or low-level driver.
> >
> > Microsoft pushes for their .net standard, and Google have their own
> > libraries and languages.
> >
> > If you already have memory leak issue, use a memory profiling tool.
> > Microsoft's diagnostic tools or vtune are good.
>
> Thanks but getting this fixed implicitly is better.
>
> >
> > Get Outlook for iOS <https://aka.ms/o0ukef>
> > ------------------------------------------------------------------------
> > *From:* Std-Proposals <std-proposals-bounces_at_[hidden]> on
> behalf
> > of Phil Bouchard via Std-Proposals <std-proposals_at_[hidden]>
> > *Sent:* Tuesday, February 14, 2023 4:11:39 PM
> > *To:* std-proposals_at_[hidden] <std-proposals_at_[hidden]>
> > *Cc:* Phil Bouchard <boost_at_[hidden]>
> > *Subject:* Re: [std-proposals] Safety checks at compile time
> >
> >
> > On 2/14/23 18:14, Bjorn Reese via Std-Proposals wrote:
> >> On 2/14/23 18:02, Roberto R via Std-Proposals wrote:
> >>
> >>> Is it possible to make C++ a memory safe language? For sure it is
> >>> possible to make it safer, at least for new code that does not use
> >>> legacy code.
> >>
> >> There is a lot of experimentation going on:
> >>
> >> https://github.com/carbon-language/carbon-lang
> > <https://github.com/carbon-language/carbon-lang>
> >
> > This is exactly what I was looking for actually. Instead of revamping
> > C++, let's properly design a new language inheriting from C++.
> >
> >> https://www.val-lang.dev/ <https://www.val-lang.dev/>
> >>
> >
> > --
> > Logo <https://www.fornux.com/ <https://www.fornux.com/>>
> > *Phil Bouchard* facebook icon
> > <https://www.linkedin.com/in/phil-bouchard-5723a910/
> > <https://www.linkedin.com/in/phil-bouchard-5723a910/>>
> > CTO
> > T: (819) 328-4743
> > E: phil_at_[hidden]| www.fornux.com <http://www.fornux.com>
> > <http://www.fornux.com <http://www.fornux.com>>
> > 8 rue de la Baie| Gatineau (Qc), J8T 3H3 Canada
> >
> > Banner <https://goglobalawards.org/ <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.
> >
> > --
> > Std-Proposals mailing list
> > 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.
>
> --
> Std-Proposals mailing list
> Std-Proposals_at_[hidden]
> https://lists.isocpp.org/mailman/listinfo.cgi/std-proposals
>
Received on 2023-02-15 02:39:52