4 ms·
The CLR is not a great target for running unmodified C code. I suspect that was included in "practically any language."
by Rusky 8y ago
The CLR is not a great target for running unmodified C code. I suspect that was included in "practically any language."
- pjmlp 8y agoYeah, Managed C++ and C++/CLI don't exist.
- Rusky 8y agoI was careful to say "unmodified." C++/CLI is hardly that. It's also not at all sandboxed the way wasm is. Why the chip on the shoulder?
- pjmlp 8y agoC++/CLI is just ISO C++ plus a couple of language extensions, you know like the Linux kernel is ISO C plus GCC extensions. I hardly see the difference. No chip on the shoulder, just an old guy that has seen dozens of VMs since the mid-80s, delved into others from earlier decades, which doesn't buy into WASM marketing.
- int_19h 8y agoYou're conflating C++/CLI with the MSVC /clr compiler switch. They're distinct. With /clr:pure (which produces CIL only, although it is allowed to use memory-unsafe features like pointers), the entirety of ISO C90 is supported on CLR, with the sole exception of setjmp/longjmp. C++/CLI adds language extensions that allow one to interact with the CLR object model from C++ code. It is only needed if you need to call into the .NET standard library, or other managed libraries - i.e. if your C code is not portable to begin with.