this post was submitted on 14 Feb 2024
563 points (98.3% liked)

Programmer Humor

19821 readers
680 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS
Feyter@programming.dev
anzo@programming.dev
BurningTurtle@programming.dev
pylapp@programming.dev
563
Sometimes I want to call malloc, just as a treat (lemmy.world)
submitted 10 months ago by verysuchaccount@lemmy.world to c/programmer_humor@programming.dev
28 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] Scrath@lemmy.dbzer0.com 3 points 10 months ago

Can you give some examples of what you consider to be the issues?

My professor said that C++ embedded compilers used to be very buggy but have matured quite a lot as of ~10 years ago while C was stable a lot longer.

Another thing I could think of is the language complexity causing higher resource usage, e.g. by including large libraries though I'm not sure about that since most of the unused stuff should theoretically get optimized out.

I guess if you don't know roughly how the internals of some C++ data types work it could cause you to accidentally use dynamic memory allocation when using strings or vectors.

On the other side, C++ style casts provide more safety as compared to C style casts and allows for usage of references instead of raw pointers to make the code generally safer.