On 2/25/26 00:35, Jason McKesson via Std-Discussion wrote:
> On Tue, Feb 24, 2026 at 8:33 PM Phil Bouchard via Std-Discussion
> <std-discussion_at_[hidden]> wrote:
>> I apologize but people forget the US government disallows memory unsafe programming languages:
>>
>> https://media.defense.gov/2025/Jun/23/2003742198/-1/-1/0/CSI_MEMORY_SAFE_LANGUAGES_REDUCING_VULNERABILITIES_IN_MODERN_SOFTWARE_DEVELOPMENT.PDF
>>
>> Given the importance of the problem I was hoping for a constructive discussion as it is free anyways for OSS projects.
> The validity of your description of that paper aside (nothing in that
> paper seems to "disallow" anything; it's just a look at the current
> state of affairs), that doesn't justify your post. This ML is for
> discussing the C++ standard as it exists. If you want to propose
> changing it, there's a different ML for that.

https://www.theregister.com/2024/11/08/the_us_government_wants_developers/


Thanks,

-- 
Email Signature
Fornux Logo <https://www.fornux.com/>  
*Phil Bouchard*  LinkedIn Icon 
<https://www.linkedin.com/in/phil-bouchard-5723a910/>
Founder & CEO
T: (819) 328-4743
E: phil_at_[hidden]| www.fornux.com <http://www.fornux.com>
720 Oliver Ave, San Diego, CA, 92109
The Best Predictable C++ Memory Manager 
<https://static.fornux.com/c-superset/> 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.