>It sucks because people miss error codes, or they overwrite them, or misunderstand what they mean. "Pointers suck", for the same reason. In any case, its the

>It sucks because people miss error codes, or they overwrite them, or misunderstand what they mean. "Pointers suck", for the same reason. In any case, its the 21st century - if you're shipping C code that hasn't been statically analyzed with 100% code coverage, you're doing it wrong. Besides which, this is an abstraction which, once done properly once, in a library or framework, can be ignored at higher levels of abstraction, or even language runtime/execution environments, with some degree of comfort .. /ducks