There is value in a simple integer error code return from public C APIs, but it would be nice to have an easy way to get the full statement that forced the return, assert-style. INVALID_VALUE is not as helpful as it could be.
-
some structure where there is a string for every error code, a function that maps one to the other or whatever, for every little thing that can go wrong. (This of course leads to the thing that happened on both Unix and Windows where the same set of error codes gets mashed
together for everything, leading e.g. to everyone's favorite useless error EINVAL.) I think the improved ergonomics of just observing how bad this all went, and setting up the incentives so that better things happen naturally, are huge (and underestimated by everyone).
-
-
(The important thing about this logging function being that it is an established convention that leaf-functionality library authors can use and they just expect the application to do what it wants with it, they don't have to build their own reporting system for each lib, etc).
-
1) log_error() only takes in a string, not an arbitrary type right? 2) By "turning it off" in release mode, do you define it to do nothing and let the optimizer handle that? Or is there some # command?
- Show replies
New conversation -
-
-
Do you talk about this subject more at length somewhere?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.