/explore
|
You are here 
|
graylab.jhu.edu | ||
| | | | |
adventures.michaelfbryan.com
Once you get past the growing pains of the Borrow Checker and realise Rust gives you the power to do things which would be unheard of (or just plain dangerous) in other languages, the temptation to Rewrite it in Rust can be quite strong. However at best, the temptation to RiiR is unproductive (unnecessary duplication of effort), and at worst it can promote the creation of buggy software (why would you be better equipped to write a library for some domain-specific purpose than the original author? |
|
| | | | | ||
| | | | |
www.copetti.org
An in-depth analysis that explains how this console works internally |
|
| | | | | ||
| | | | |
www.cppstories.com
Let's say we have the following code: LegacyList* pMyList = new LegacyList(); ... pMyList->ReleaseElements(); delete pMyList; In order to fully delete an object we need to do some additional action. How to make it more C++11? How to use unique_ptr or shared_ptr here? Intro We all know that smart pointers are really nice things and we should be using them instead of raw new and delete. |
|
| | | | | ||
| | | | |
wiki.osdev.org
[AI summary] A step-by-step tutorial from the OSDev Wiki explains how to parse and implement an ELF file loader for the i386 architecture using C code. |
|
| | | |||
