> People would deem this impossible with C for practical purposes, but I think it's just a matter of responsibility, discipline and devotion. When do you reach

> People would deem this impossible with C for practical purposes, but I think it's just a matter of responsibility, discipline and devotion. When do you reach the point of saying "ok, that's enough discipline and devotion" and how do you know that what you've done is indeed enough? Is there a study on "subjective quality of software written in C vs number of actual security vulnerabilities"? I think that would help shed some light on the real world implications of that particular mindset many C programmers tend to have :)