this post was submitted on 29 Dec 2024
332 points (98.8% liked)
Programmer Humor
19887 readers
411 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
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Because stuff can own other stuff and be owned at the same time. Also, arcane jackarsery.
Edit: if you want to give a function a pointer that it may change this may occur in a constructive way. I.e. replace an owned object.
Yeah... But it's usually a good practice to put a struct somewhere between your 30 levels of ownership.
Exceptions exist, but they are not very common. Also, in C++, operators overloading may help you if you keep needing to write code like this.
In C++ you should never have owning raw pointers. Unless you have a good reason™.
Raw pointers are great, but not for ownership.
I just use
unique_ptr99% of the timeAnd you should.
It even works for classes whose constructors your implementation cannot see, if you aren't a bitch about it.