>>95
but being able to raise a value and handle it elsewhere with a dynamically bound exception handler.
I'm honestly OK with that value just being a string or some error code or something. when I write in languages without exceptions, the thing I miss is not having to "thread up" the error, not the handling code. Most of the time the error handling isn't much more than printing it somewhere. Who actually puts a large amount of code in catch blocks? I'll just write an (unless ) or something checking for error.
I never said call/cc was a synonym of continuations. I've implemented call/cc (and continuations) for DSLs in C a couple of times. I've worked extensively in Java and C++. I've used setjmp to get something like exceptions in C. I get this shit. I just don't find exceptions as they are presented in C++ and Java to be useful. I actually prefer coroutines to exceptions (as far as things you can implement with continuations goes.) Deal with it.