4 ms·
rundll32.exe is just a way of doing FFI from as a command -- there are few different options on UNIX-likr systems for that. The most obvious is ctypes.sh [0].
by rkeene2 4y ago
rundll32.exe is just a way of doing FFI from as a command -- there are few different options on UNIX-likr systems for that. The most obvious is ctypes.sh [0].
There are, though, even more sophisticated options than just FFI, like the Witchcraft Compiler Collection [1], which includes among other things an interactive shell.
[0] https://github.com/taviso/ctypes.sh https://github.com/taviso/ctypes.sh
[1] https://github.com/endrazine/wcc https://github.com/endrazine/wcc
- _8j50 4y agoI'm just surprised there isn't a standard, even POSIX utility to run shared libs but by calling specific functions. It would avoid the need for executables that just wrap a few api's in the shared lib.
- 4ad 4y agoPOSIX doesn't require shared libraries at all.
- _8j50 4y agoNow that is a TIL! I thought it was more specific than that.
- mncharity 4y ago> I'm just surprised there isn't a standard Standardization seemingly has windows, which if missed, make it far less likely and harder. Even when a need is recognized - eg, python's years of struggle to create a central module repository. But especially when you hit "why would anyone want that?!?" and "we don't approach things that way" barriers. I recall many years back... dlopen/dlsym can redirect through a lazily-set lookup table, so a seemingly obvious thing to want, is to reset table entries, for live reloading. Given a very simple lookup table, value setting didn't seem a bizarre ask. But "changing a binding?!?" and "there's no standard spec" and "intriguing, but why?" and... I'd not be surprised if it never happened. I love to see a sketch of the "how hard is it to standardize something, and what you can do about it" space.