3 ms·
You're considering the "call into C" case, which is only half the story. "C calls into you" will always be easier in C++ and Rust, or any other language with "n
by steveklabnik 9y ago
You're considering the "call into C" case, which is only half the story. "C calls into you" will always be easier in C++ and Rust, or any other language with "no" runtime, than heavier languages that rely on them. Yes, it can work, but it's a disadvantage.
- Const-me 9y agoIn C# I use callbacks where I find appropriate (logging, also some rare events). Under the hood, the runtime marshals delegates (most languages would call them lambdas) into unmanaged C function pointers. Ease of use is the same when I consuming the C API from e.g. C++. No disadvantage for C#.
- sinhpham 9y ago"C calls into you" means you already have a C code base and now need to call your C# functions.
- Const-me 9y agoRight, C# is OK when C code calls into it. https://stackoverflow.com/a/5235549/126995 https://stackoverflow.com/a/5235549/126995
- steveklabnik 9y agoTo be clear, I’m not saying it’s not possible. I’m saying that one less runtime is an advantage.
- int_19h 9y agoOne neat trick with .NET on Windows, is that you can actually export static methods in assemblies as unmanaged entry points. In other words, things can LoadLibrary/GetProcAddress them, and invoke them as native. C# doesn't support this out of the box, but it can be easily done by post-processing the generated assembly. There's a NuGet package for that. https://www.nuget.org/packages/UnmanagedExports https://www.nuget.org/packages/UnmanagedExports I'm not sure if any of that works on other platforms, or with .NET Core. Probably not.
- Const-me 9y agoI once tried to use that trick, for nVidia optimus integration. Didn’t work because that recompilation step broke debugger, and invalidated .PDB debug symbols.