freenode/#sicl - IRC Chatlog
Search
16:06:41
Bike
if i remember correctly the problem i hit was that foreign exceptions can't... nest? like you can't throw a non-C++ exception while handling one
16:06:48
Bike
"Nested foreign exceptions, or rethrowing a foreign exception, result in undefined behaviour. " yeah, that
16:07:11
Bike
and i think the reason for that is that the chain of exceptions is stored in the __cxa_exception object instead of the non-language-specific object
16:08:46
Bike
and the other problem is this wouldn't actually improve performacne because exceptions would stillb e slow. right. can't forget that
16:11:00
Bike
shinmera's idea of only using C++ exceptions if there are actually relevant C++ frames would probably be best for performance
16:31:28
phoe
the current exception handling proposal should not really be modified because it needs to get delivered for C++ people
16:32:03
phoe
my proposal is mostly orthogonal to exception handling because it mentions non-local control flow, and therefore it should be processed as a separate wasm proposal
16:32:38
phoe
I'll edit my post to take this into account, run it by this person and by Ioanna, and then think of how to go forth with it
18:53:24
phoe
it would be even better to have a full blown CL in WASM compiling into more WASM and capable of loading it
21:09:46
mseddon
phoe: that's great news! if there's any way I can help support this proposal, let me know!
21:12:48
mseddon
to be fair I am actually quite out of the loop on the status of the current exception handling proposal. I should probably swing by and see how that looks...
23:03:32
Bike
ecl can compile lisp to C and doesn't use C++ exceptions, right? sounds like a good choice
23:10:46
phoe
funny thing: a proper control flow proposal will be required to correctly handle C's longjmp