Articles

(Apr 29) #cpp Save to Pocket

With the introduction of smart pointers in C++11, it seems like a lot of people lost sight of why they were introduced, preferring to justify their abuse of the new feature with the idea that it's easier and safer. Albeit partially true, the idea of ownership is important, and that's exactly what George Hosu discusses in this informative article. George gives examples of when unique pointer, shared pointer, and weak pointer should all be used, in the context of a widget implementation.

(Mar 25) #cpp Save to Pocket

Ever wanted to learn how to hack a game? Or just see an example of some exceptional reverse engineering? Well the author of this article, exploit, has written a thoroughly detailed guide on how he built an aimbot for Doom95. Starting with downloading the game and playing it, the author walks through how they found the places in memory where health and coordinates are stored, and their implementation of the aimbot in C++. A summary can't do this extensive article justice, so check it out yourself!

(Mar 19) #go Save to Pocket

Every language has its intricacies. The sooner you learn them, the less errors and bugs you might run into. Lots of these little errors and bugs might appear when you're messing with variables in loops. Chris Siebenmann has written an article about a recent minor (but fundamentally major) point he came across, that ranges in Go are done on copies of the original arrays. Chris points out the problems that might arise from this in the context of copying data.

And that's it for today! Discuss this issue at our subreddit r/morningcupofcoding.

Did you like what you read? Let us know by clicking one of the links below.

Liked - Disliked

I hope you enjoyed reading the latest issue of Morning Cup of Coding. If you did, consider supporting us by becoming a patron (Patreon) for perks like ad-free issues, or via a one-time donation via PayPal.

Interested in sponsoring our newsletter? Click here to send us an email.

Cheers,

Pek