Search
Friday, 3rd of February 2023, 11:10:49 UTC
11:51:08
selwynning
hm i can't use the js runtime, which seems irreplaceable
11:53:55
selwynning
what are my options?
11:55:10
selwynning
i considered targeting wasi-sdk instead but the virtual file system etc aren't going to be easy to replace
11:56:35
jackdaniel
fwiw wasi is generally the next step I want to do after emscripten is merged
11:56:44
selwynning
if i replace the syscalls with stubs - am i likely to be able to start up ecl?
11:56:50
jackdaniel
(i.e using standard toolchain without emscripten emcc hackery)
11:57:03
selwynning
to be clear getting ansi compliance is not the priority here
11:57:23
selwynning
i can accept having no virtual file system
11:57:39
selwynning
hm well it's nice to know targeting wasi is possible
11:58:00
jackdaniel
I don't see any fundamental reason why ecl wouldn't work without filesystem per se
11:58:14
jackdaniel
there are probably multile fixable assumptions in the codebase though
11:59:11
jackdaniel
it will be tough without read and write, but if you are not interested in a default repl then that should also be avoidable in principle
12:00:13
jackdaniel
targetting wasi has a few benefits, but it will require us to maintain a call stack and port a garbage collector
12:00:42
jackdaniel
that's why I've settled initially on the easier emscripten target
12:05:09
jackdaniel
that's true (wasi that is)
13:16:34
selwynning
is the emscripten port all your own work?
13:19:26
jackdaniel
as you can see in the pull request thread, Marius grokked it and provided very insightful remarks
13:24:37
selwynning
i was wondering if there was anyone else i could bother about this
13:24:45
selwynning
i don't like to take up your time
13:25:20
jackdaniel
don't worry about it, when I'm overloaded I'll simply won't answer ,) or answer with bigger delay
13:26:25
jackdaniel
and if you'll be at els then I'll demand a free beer ;p
Friday, 3rd of February 2023, 23:10:49 UTC