Open sdilts opened 5 years ago
Most of these functions also set errno
to indicate how the function failed. Is that something that should be left up to the caller to check, or should we try to interpret it in the error we return?
I think this sounds like a great idea. Since most C functions have weird names I think it would work well to keep those around but use more lispy names for the safe ones.
Many C library functions return a null pointer on error, i.e.
malloc
andfopen
, etc. To make these more safe, their return values should be wrapped in aResult
type.