faster and less memory overhead is good, but not always crucial; "finds some errors valgrind doesn't" is vague at best, I'd like to know the details. What's worst, I attempted to compile these tools under my CentOS 5.8 64bit, gcc 4.4, I spent 30 minutes on it and didn't have it done. Then I stopped trying.
Fair point ! C is supreme for anything that needs any kind of long term reliability, stability and sanity. Languages aren't implemented in C++ for a reason : ABI !
I found the moderators nonsense nagging of C/CPP and the first question raised in regard of Python and the answer hilarious. _"Languages most of us work with, say Python for example ... generally ... we don't worry about address, wrong address or memory sensitization, but we do worry about thread issues."_ *This statement alone shows that you are not programming. What you do is scripting fragile abstraction cathedrals that have close to zero functional maintainability but useless data abstraction, which systematically destroy data-coherence and thus tenfold power requirements. Oh and you do not even have concurrent thread execution. Haha!*
Documentation for these sort of tools is key.
Great report and great t-shirt!
faster and less memory overhead is good, but not always crucial; "finds some errors valgrind doesn't" is vague at best, I'd like to know the details. What's worst, I attempted to compile these tools under my CentOS 5.8 64bit, gcc 4.4, I spent 30 minutes on it and didn't have it done. Then I stopped trying.
How are these tools different from valgrind? What more do they offer?
your program runs much quicker and it picks up more errors, but it's a pita is you have build everything with msan enabled
The only 'language' implemented in C++ so far is Rubinius. Don't talk about C and C++ like they are the same thing. They aren't.
Fair point ! C is supreme for anything that needs any kind of long term reliability, stability and sanity. Languages aren't implemented in C++ for a reason : ABI !
See 7:00
I found the moderators nonsense nagging of C/CPP and the first question raised in regard of Python and the answer hilarious.
_"Languages most of us work with, say Python for example ... generally ... we don't worry about address, wrong address or memory sensitization, but we do worry about thread issues."_
*This statement alone shows that you are not programming. What you do is scripting fragile abstraction cathedrals that have close to zero functional maintainability but useless data abstraction, which systematically destroy data-coherence and thus tenfold power requirements. Oh and you do not even have concurrent thread execution. Haha!*
Кровь из ушей от этого акцента