freenode/#clasp - IRC Chatlog
Search
20:04:43
Bike
...right, all my changes were reverted as part of something else. i am going to do that again and it will stick
21:17:36
Bike
hoo, i thought i hit a bug that was going to be hugely irritating to find, but worked it out. go two minute breaks
21:20:38
Bike
and another quick survey shows they make up a little over half of all the single-method case
21:54:59
Bike
But when we call the fast method function we need the closure to be the fast method function.
21:56:00
drmeister
Bike: If you aren't tied up with something else - could you come be a sounding board to my latest exception handling problem.
21:56:16
drmeister
I keep upping my game with the debugging but eh seems to be one step ahead of me every freaking time.
2:23:41
drmeister
I'm pretty sure there is a very long standing problem lurking in Clasp's exception handling when exceptions are thrown in cleanup clauses. I'm pretty sure it has something to do with cxa_begin_catch/cxa_end_catch/rethrow
2:24:25
drmeister
I might be failing to pop entries from the exception stack - it would be really useful if I could interrogate the exception stack - must look into it.
3:03:14
beach
Common Lisp signals are a model of simplicity compared to the description of C++ exception handling in that article.
3:04:38
drmeister
Yeah - unfortunately everything rests on me figuring out the C++ exception handling. It's amazing that I got it almost right but not quite.
3:05:07
beach
Bike: Yes, you are right, some optimizations are possible because we always have all the code at our disposal, so they resemble static optimizations. When the code changes, we just adapt to the new version of the entire code.
3:05:44
beach
Bike: I am pretty sure there are many other such optimization opportunities to explore.