Explore >> Select a destination
|
You are here 
|
etherealwake.com | ||
| | | | |
quuxplusone.github.io
|
|
| | | | | In C++, there's often multiple ways to refer to the same entity: aliases, inherited names, injected names, names that differ in qualification... Usually, if an entity has multiple names, which one you use won't matter: you can use any of those synonymous names and the compiler won't care. But each entity always has a uniquely "truest" name, privileged above all the other ways to refer to it. In some situations, in order to do a thing with an entity, you do actually need to call it by its "true name." Here is a (non-exhaustive) list of such situations. | |
| | | | |
buchanan.one
|
|
| | | | | An introduction to C++ build systems focused on building fundamental understanding. | |
| | | | |
chadaustin.me
|
|
| | | | | [AI summary] This article discusses creating C++ DLL interfaces that ensure binary compatibility across different compilers and configurations by using virtual methods, extern "C" for function declarations, and managing memory allocation to prevent crashes due to incompatible heaps. | |
| | | | |
deepmind.google
|
|
| | | This has been a year of incredible progress in the field of Artificial Intelligence (AI) research and its practical applications. | ||
