#C and C++ preprocessor for modern memory safety

7 messages · Page 1 of 1 (latest)

rain onyx
dreamy spindle
#

Calling Go out here is weird because it doesn't have manual control of pointers or allocations to where memory safety would be a problem

#

Zig is also weird because it has exactly the same issues as C in terms of safety. The language just doesn't make it as aggressively easy to do stupid mistakes, but forgetting things and using things incorrectly is still very possible

dreamy spindle
#

Also why is the build driven by a C file...

#

Blindly replacing code in files seems like a bad idea especially for a language whose syntax is as complicated as C

frank elbow
#

Next-Generation Memory-Safe Preprocessor