That is a library issue. Trying to make C 'foolproof' however, is an excercise in futility, and in any case, can only come about by morphing it into a fundamentally different language. An argument in this thread, is…
And yet, it clearly does (work). When it doesn't (work), it is NOT because of a failure in the language; It is because C has (and always will have) the "basic philosophy that programmers know what they are doing;".…
"C retains the basic philosophy that programmers know what they are doing; it only requires that they state their intentions explicitly." The real 'mistake', is programmers not stating their intention explicitly.
That is a library issue. Trying to make C 'foolproof' however, is an excercise in futility, and in any case, can only come about by morphing it into a fundamentally different language. An argument in this thread, is…
And yet, it clearly does (work). When it doesn't (work), it is NOT because of a failure in the language; It is because C has (and always will have) the "basic philosophy that programmers know what they are doing;".…
"C retains the basic philosophy that programmers know what they are doing; it only requires that they state their intentions explicitly." The real 'mistake', is programmers not stating their intention explicitly.