17:48:18edgar-rftYes, it's Matt Groening who now names trains.
17:52:25drmeisterfrgo: I hope to be able to work hard on cffi to finish it up this coming week. I've almost got the cclasp backtrace issue licked
18:00:16drmeisterI've decided to implement the solution as setting up cclasp generated functions as having one of four permutations of exception handling. Yeah - one of four.
18:02:45drmeister1: no exception handling. 2: a backtrace frame. 3: the function is the target of an UNWIND instruction. 4: 2 and 3 together.
18:04:54drmeisterIt's like a C++ function with no try/catch. Or one or two nested try blocks. One try block cleans up the backtrace frame and the other handles UNWIND
18:05:19drmeisterAs I'm writing this I'm getting anxious about the complexity.
18:52:20frgodrmeister: Well, following only partly here - not deep enough in the subject. Why not only do nr 4 as the most general case?
19:06:55drmeisterRuntime overhead is added by each level.
19:07:49frgoI figured as much. I didn't understand why there's the need for a backtrace frame, though, in variant 2
20:52:34drmeisterGetting backtrace with arguments passed to the function is very valuable for debugging.
20:53:58drmeisterThe only way I have right now to achieve that is to spill the arguments into a structure in the stack frame and push a pointer to that structure on entry to function and pop it on exit.