2024-03-12 10:15:21 <veltas      > Does anyone in here actually 'get' webassembly and has done anything with it?
2024-03-12 10:16:46 <veltas      > Also it should be really called WebBytecode or WaitItsAllLisp?AlwaysHasBeen or something
2024-03-12 11:30:44 <MrMobius    > Makes sense to me more or less. I've played with it. I was thinking about compiling part of an existing C program to a custom bytecode to interpret on a microcontroller
2024-03-12 11:31:14 <MrMobius    > So webassembly makes sense for that
2024-03-12 11:50:07 <veltas      > Today I leanred Bill Gates was obsessed with APL
2024-03-12 18:21:57 <Al2O3       > today I learned veltas is obsessed with Bill Gates
2024-03-12 18:28:24 <rendar      > i have implemented in my Forth a try/catch for catching errors, do you think i should clear the stack inside a catch scope?
2024-03-12 18:33:55 <zelgomer    > try/catch as i've seen it before restores the stack pointer to where it was before the try. anything that was above that is lost, and if the stack had dipped below that then the space between is undefined.
2024-03-12 19:08:30 <veltas      > And I personally think that's the right way to do it
2024-03-12 19:08:55 <veltas      > The standard mechanism also saves and restores the input state, so exception thrown in a file can be caught by block code, etc
2024-03-12 19:09:50 <veltas      > Although I'm not sure how much of input state is restored, i.e. would it restore >IN back to CATCH state?
2024-03-12 23:03:46 <remexre     > oh, I've been tinkering with wasm for the last couple weeks, yeah
2024-03-12 23:04:47 <remexre     > I'm trying to replicate JSLinux for RV64 on top of wasm, and then see if I can add a "mostly AoTed" mode that works for both the emulated kernelspace and userspace
2024-03-12 23:37:29 <veltas      > I don't fully understand what you said but it sounds very impressive