Re:The empire of C++ strikes back with Safe C++ blueprint
by vacuity on Sunday October 20, 2024 @10:21PM
(#41900165)
It isn't what is explicitly touted as standard, but it is what many developers have culturally established.
Re:The empire of C++ strikes back with Safe C++ blueprint
by eacnamn on Monday October 21, 2024 @01:11PM
(#41906160)
>That's absolutely not the C/C++ philosophy
while it is not explicitly written out like this anymore, the standard charter used to say
> Trust the programmer.
> Don't prevent the programmer from doing what needs to be done.
for 30 something years, which sounds similar to what the other poster said.
The current charter[1] only says "Allow programming freedom" which I'd still interpret to mean something similar.
1: https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3280.htm
(edited due to formatting messups)
Re:The empire of C++ strikes back with Safe C++ blueprint
by 29athrowaway on Tuesday October 22, 2024 @05:08PM
(#41918715)
Some freedom is productive, some freedom is not.
That's absolutely not the C/C++ philosophy. The C philosophy (I lost track of whatever the C++ philosophy is supposed to be several versions back) is that it's a mid-level language and lets you have pretty low-level access to the machine. With that comes the need for great caution, much like working in assembly.
It's not premised on the idea that programmers are infallible at all, but on the idea that code-checking and correctness is to be done through process rather than the language itself.