Object Pascal does not support multiple inheritance.OK,C++ is more complex than I can understand.Thanks to your advice.
(even Bjarne Stroustrup, the creator of C++, thought that was a really bad idea with hindsight)
BUT...You can mimic it with interfaces.
Also, It is very rare in C++ circles that it is used, let alone used correctly.
It is the single most unloved "feature" of C++.
Using interfaces - in this case COM or CORBA does not matter - leads to easier to understand and maintain code. (Bjarne said so)
I wasted half of my life writing C and C++ code and only 25% writing Pascal and never needed that.
https://stroustrup.com/bs_faq2.html
https://www.usenix.org/legacy/publications/compsystems/1989/fall_stroustrup.pdf
So idiots that claim to the contrary can shut up immediately.
>:( >:D O:-)
If Bjarne says no, and you still want to use it, you are an idiot.
Note I documented it undeniably so don't even bother to reason otherwise.
So idiots that claim to the contrary can shut up immediately.I have used it sometimes by inheriting (multiple) pure virtual classes in purpose to mimic the D/FPC interfaces. :-[
>:( >:D O:-)
If Bjarne says no, and you still want to use it, you are an idiot.
Note I documented it undeniably so don't even bother to reason otherwise.
I think.Are you sure? :-X
Quite sure. Pure virtual classes inherited as interfaces.I think.Are you sure? :-X
Using interfaces - in this case COM or CORBA does not matter - leads to easier to understand and maintain code. (Bjarne said so)
]BUT...You can mimic it with interfaces.Good luck.
I told you so:No, it is the other way around - using C++ MI with pure virtual classes in place of FPC interfaces. --Bjarne said so.Quote]BUT...You can mimic it with interfaces.Good luck.
NO
Good luck,
Also, It is very rare in C++ circles that it is used, let alone used correctly.
It is the single most unloved "feature" of C++.
C++ is not complex, but multiple inheritance is - or can be - complex. And stupid.However,C++ grow more complex as many features announced in C++23 and later standard published.I think long history open-source C/C++ projects like binutils will use C++11 standard as the main standard to write the code.
( like with in Pascal)
I think long history open-source C/C++ projects like binutils will use C++11 standard as the main standard to write the code.
However,C++ grow more complex as many features announced in C++23 and later standard published.I think long history open-source C/C++ projects like binutils will use C++11 standard as the main standard to write the code.It is not multiple inheritance (which is C++ only and not C) The C standards can't be flawed for that.
So in your view what the C++ standard newest version of open-source C/C++ projects like binutils will use(I am writing my C2pas,so I want to know what feature in C++ will be used in these projects)?
C++ exists in the newer version of binutils.gold(elf-only linker) is developed using C++,we cannot guarantee whether C++ developers join in GNU organization.I think long history open-source C/C++ projects like binutils will use C++11 standard as the main standard to write the code.
GNU Binutils is written in C, not C++ and they won't simply change the language, so if at most they'll change to newer versions of the C standard. But even then the developers will very likely restrain themselves, because GNU Binutils are also available for older systems that don't support newer C standards.
So you are not referring to the compiler, but that the gold linker has C++ support?Yes,my developing c2pas is specialized to C projects such as binutils.
The old linker has also C++ support..... You mix things up.