Re:Nvidia Security Team: "What if we just stopped using C?" ...
by bluGill on Friday February 14, 2025 @08:39AM
(#43048124)
now interoperability costs performance for all the serialize/deserialize operations and so the language is too slow to be practical.
Re:Nvidia Security Team: "What if we just stopped using C?" ...
by sitzkrieg on Friday February 14, 2025 @04:51PM
(#43053480)
not an ada issue
Re:Nvidia Security Team: "What if we just stopped using C?" ...
by MaxBarraclough on Friday February 14, 2025 @06:24PM
(#43054179)
The bookkeeping overheads might be trivial though. If it boils down to a handful of instructions per call, that's probably not so bad, depending on context. If large buffers are being copied, that's a problem, but hopefully that can generally be avoided.
Re:Nvidia Security Team: "What if we just stopped using C?" ...
by MaxBarraclough on Friday February 14, 2025 @06:25PM
(#43054186)
> There are a few languages that interop with C++ at a deeper level, essentially building a small part of a C++ compiler into their runtime
The other approach is to compile to C++ source.
There are a few languages that interop with C++ at a deeper level, essentially building a small part of a C++ compiler into their runtime. But they're relatively obscure - Clasp, an implementation of Common Lisp, is probably the only one that can really take an arbitrary C++ object (say, an std::vector<std::list<int>>) as an input to a Common Lisp function and work with it.