On 9 Jul 2001, Ian Holsman wrote: > maybe there needs to be a method of registering error numbers/functions > so that apr_sterror knows that error 1230981 is from apr-util and would > call apr-util's function it registered to show the error message.
hee! sorry, just thinking back to discussions several years ago. even within a typical libc there are at least two error mechanisms -- errno/strerror(), herrno/hstrerror(). if you're using glibc then you've also got gdbm_error/gdbm_strerror(). if you use zlib theres an error with each file handle and gzerror() to get the string. the list goes on. btw, an alternative to trying to define an exception mechanism for C (which i *think* you'll end up if you continue thinking about this) is to combine apr and apr-util into one library so they can just do their "registering" at compile time :) -dean
