Date: Sun, 12 Feb 2023 12:50:59 -0500
On 2/12/23 12:44, Jens Maurer wrote:
>
>
> On 12/02/2023 18.38, Phil Bouchard via Std-Proposals wrote:
>>
>>
>> On 2/12/23 12:34, Thiago Macieira wrote:
>>> On Sunday, 12 February 2023 09:31:09 PST Phil Bouchard wrote:
>>>>> In other words, you've already solved your problem without any need to
>>>>> change the standard. What else is left?
>>>>
>>>> That solution is only temporary because who knows is Google plans to
>>>> maintain TC Malloc forever?
>>>
>>> What does that have to do with the C++ standard? What if Microsoft stops
>>> maintaining Windows? What if the C++ committee decides to close up shop?
>>
>> Well isn't the goal of having ISO standards to make not only
>> maintainable applications but perfectly robust as well?
>
> The goal of the ISO C++ standard is primarily to enable portability of
> applications between one implementation (compiler, linker, hardware etc)
> and another.
It's clearly more than that. All the abstraction efforts with or without
Boost community's help I think is pretty good. One of my favorite being
parallel loops:
https://en.cppreference.com/w/cpp/algorithm/execution_policy_tag
Good job on that one.
>
> Beyond that, different people in the committee have different opinions
> what is in-scope for that portability goal and what isn't.
>
> Oh, and I don't know what you mean by "perfectly robust".
Perfectly robust means to drop cybersecurity issues related to memory
allocation issues which is currently 70% down to 0% just by using the
cutting edge standards.
>
> Jens
>
>
> On 12/02/2023 18.38, Phil Bouchard via Std-Proposals wrote:
>>
>>
>> On 2/12/23 12:34, Thiago Macieira wrote:
>>> On Sunday, 12 February 2023 09:31:09 PST Phil Bouchard wrote:
>>>>> In other words, you've already solved your problem without any need to
>>>>> change the standard. What else is left?
>>>>
>>>> That solution is only temporary because who knows is Google plans to
>>>> maintain TC Malloc forever?
>>>
>>> What does that have to do with the C++ standard? What if Microsoft stops
>>> maintaining Windows? What if the C++ committee decides to close up shop?
>>
>> Well isn't the goal of having ISO standards to make not only
>> maintainable applications but perfectly robust as well?
>
> The goal of the ISO C++ standard is primarily to enable portability of
> applications between one implementation (compiler, linker, hardware etc)
> and another.
It's clearly more than that. All the abstraction efforts with or without
Boost community's help I think is pretty good. One of my favorite being
parallel loops:
https://en.cppreference.com/w/cpp/algorithm/execution_policy_tag
Good job on that one.
>
> Beyond that, different people in the committee have different opinions
> what is in-scope for that portability goal and what isn't.
>
> Oh, and I don't know what you mean by "perfectly robust".
Perfectly robust means to drop cybersecurity issues related to memory
allocation issues which is currently 70% down to 0% just by using the
cutting edge standards.
>
> Jens
-- 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-12 17:51:01