Tue Jan 30 21:19:32 GMT 2007

error handling

maybe the most important one is error handling.. that's really
broken. the real problem is that everywhere in the code, a simple
return value is used for error handling.

what about turning these things into objects? there are 2 ways to
generate an error:

1. return e_error
2. THROW(e_blabla, "message")

this should be not so difficult, as long as nothing gets lost. a place
where things could get lost is in using EXEC and ignoring the error.

so. i just changed all EXEC occurances in libpf/libpf to either a TRY
or a TAIL case. all of those should respect conservation of error.