3 ms·
Is that a likely problem for the kernel, actually? Given that there's no API stability, and the fact that syscalls are an explicit ABI anyway, I don't see how t
by anarazel 9y ago
Is that a likely problem for the kernel, actually? Given that there's no API stability, and the fact that syscalls are an explicit ABI anyway, I don't see how that'd matter for linux?
(not that I'm arguing for C++ in linux or such)
- rileymat2 9y agoSorry, Just my sour grapes. Recently created a third party SDK DLL in c++ and could not pass c++ types natively (unless you coupled to compiler and maybe version of compiler).
- gmueckl 9y agoThis is C++ on Windows for you. On Linux, most compilers follow the ABI that GCC created, which has become very stable. I actually cannot name a C++ compiler that doesn't follow that ABI.
- cesarb 9y agoActually, Linux nowadays uses the Itanium C++ ABI (even on non-IA64 architectures), and AFAIK it was created by Intel, not GCC.
- gmueckl 9y agoI stand corrected. Indeed, the Itanium ABI defined by Intel is the base. The important part is that it is used by most, if not all, C++ compilers on that platform.
- pjmlp 9y agoWhich is why any Windows developer that wants to export OO libraries uses COM instead, with the benefit that any Windows compiler that can speak COM is able to use the library. UWP now even supports generics and actual inheritance.
- garmaine 9y agoKernel modules?
- ihalip 9y agoWhen using C++, you also need to take into account the compiler ABI.
- clappski 9y agoDoes that really matter in the context of the Linux kernel, seeing as GCC is the only supported compiler currently?