On Tue, 11 Jul 2006, Attilio Rao wrote: > Even if I have no proof-of-concepts (so maybe somebody can show that > this is not fair), if we have setjmp/longjmp in the kernel we can have > a correct exception handling mechanism without not great problems.
You'd think that, but at least one issue is that not all kernel resources are manageable via RAII*. So whilst you might be able to stack unwind, you're still left with a really hairy resource management problem - potentially at every frame - which often doesn't improve on the error checking and throwing idioms as expressed in C. I think it'd be interesting to try to address this but "I don't think you want to start from here". jan * for the non-C++ buffs, "Resource Acquisition Is Initialisation": using automatic variables of types with destructors that clean up the underlying resources when they go out of scope. -- jan grant, ISYS, University of Bristol. http://www.bris.ac.uk/ Tel +44 (0)117 3317661 http://ioctl.org/jan/ YKYBPTMRogueW... you try to move diagonally in vi. _______________________________________________ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
