2 ms·
"Systems programming language" is a loaded term, IMO. Many people have used C - probably the canonical systems programming language - inappropriately for applic
by barrkel 17y ago
"Systems programming language" is a loaded term, IMO. Many people have used C - probably the canonical systems programming language - inappropriately for applications where better languages would have been more suited. We've paid the price in insecurity, buffer overflows, memory errors, etc. many times over. I think you need to more clearly define what you mean by it.
You can't mean very low level programming, since that is a very small fraction of all programming - and probably not the best domain of a general purpose programming language.
As I mentioned in another comment in this thread, I see exceptions as exactly equivalent to a rigorous approach to error codes.
I also note with interest that you describe the form as "handle the error and pass up an error code". This reads to me as a contradiction in terms. While the error code is still propagating, the error has not been handled. Some intermediate cleanup has perhaps been done, but normal code execution has not yet resumed. Moreover, exceptions have mechanically checkable formalisms for these phases of error handling.