So why use it?
Strange, I use C instead of C++ and don't have "typical C memory access
errors". What are you referring to, specifically?
I suspect he meant such things as attempting to dereference a pointer to
NULL or to the "wrong" area of memory, forgetting to deallocate memory
(memory leakage), reading/writing past the end of an array or memory
buffer, ...
C++ does have mechanisms lacking in C to assist in avoiding these errors,
such as the ability to do memory allocation/deallocation in
constructors/destructors, overloading of operators to implement array
bounds checking and ...
How does it make it more robust? Do you really mean that it helps
programmers who don't know C and pointers very well?
It is possible, but you have to be almost wilfully perverse, to initialise
a reference with a NULL/invalid address.
Is it excessive, or not?
Perhaps "consistent usage wherever appropriate" might have been a better
phrase
Ah, so you don't have C-literate programmers. You might want to
investigate how ADT's are properly implemented in C.
Perhaps "properly implementable" might be more accurate. I would suggest
that C++ makes encapsulation and object access control easier than it is
in C.
That's ok, embedded platforms always have plenty of memory.
Who "abuses" embedded software, other than the implementor(s)?
The authors of software which accesses an API/interface to an embedded
system? I think what was intended is that it's easier in C++ than in C to
close off avenues of possible "abuse" - eg. by not exposing data/methods
that should not be accessed by the user of an interface to your system.
I'd prefer "more easily than can be achieved in C".
Not true. Perhaps you meant to write "I" instead of "you".
Possibly that too
