Stensal SDK: Retrofitting C/C++ code with quasi-memory-safety

Re:Stensal SDK: Retrofitting C/C++ code with quasi-memory-sa... by swiftcoder on Sunday January 13, 2019 @11:17PM (#18900601)

How does this differ from valgrind in practice?

[ Parent | on HN ]

Re:Stensal SDK: Retrofitting C/C++ code with quasi-memory-sa... by stensal on Monday January 14, 2019 @12:09AM (#18900822)

Ok, The following is the highly level goal. It dictates the design choice and hence the user experience of Stensal SDK.

I want to make C/C++ more user friendly and less scary to beginners. If you love C, you should keep enjoying coding in C and worry less about the memory safety issues. With the advancement of tooling (You will see more advanced static analyzers and runtime analyzers coming out from academia and the industry), it will be less a problem in the future.

The simplicity and portability of C is its key strength that no other languages have. Once the memory safety issue is alleviated, the simplicity of C will help us to build less complex but more functional and reliable code.

C++ is just a completely different beast that I have to support.

[ Parent | on HN ]

Re:Stensal SDK: Retrofitting C/C++ code with quasi-memory-sa... by Matthias247 on Sunday January 13, 2019 @11:33PM (#18900671)

and memory/address-sanitizer, which are super helpful too

[ Parent | on HN ]

Re:Stensal SDK: Retrofitting C/C++ code with quasi-memory-sa... by stensal on Monday January 14, 2019 @12:16AM (#18900849)

If ASAN/MSAN works for you well that's great.

You want to give Stensal SDK a try, you will find it's easier to use provided Stensal SDK can build your code. If you have any problems, feel free to send bugs report to [email protected]. What communication method do you prefer? a mailing list.

[ Parent | on HN ]