this post was submitted on 26 Feb 2024
267 points (96.5% liked)
Programming
17432 readers
220 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities [email protected]
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Fixed that for you. There's no situation where you want buffer overruns.
Fixed further?
It's perfectly possible to write C++ code that won't fall prey to buffer overruns. C is a lot harder. However yes it's far from memory safe, you can still do stupid things with pointers and freed memory if you want to.
I'll admit as I grew up with C I still have a love for some of its oh so simple features like structs. For embedded work, give me a packed struct over complex serialization libraries any day.
I tend to write a hybrid of the two languages for my own projects, and I'll be honest I've forgotten where exactly the line lies between them.
I want buffer overruns in my game consoles for jailbreaking purposes lmfaoooooo