13 points
I guess you could call this an OOPsie
1 point
2 points
13 points
Repeat after me: public static void main(String[] args)
3 points
public static void main(String[] args)
public static void main(String[] args)
public static void main(String[] args)
Am I summoning the flying spaghetti monster?
2 points
2 points
9 points
*
8 points
*
I straight up never got a nice answer from StackOverflow on this. Say you have 5 classes, each requiring access to the data members/functions of the others. What’s a nice way to solve this problem? I’ve thought of only two nice shit methods:
- Pass pointers/shared-pointers etc to each class, but not through the constructor but a setter function
- Pass lambdas or std::function everywhere. Yuck! Still doesn’t put each object in a valid state in the constructor.
11 points
11 points
5 points
Does external logging not happen outside of OOP?
If so, why not?
3 points
21 points
I misread Exceptioncatcher as Exceptionhatcher and I think it still fits
5 points
I believe the lifecycle goes ExceptionLayer, ExceptionIncubator, ExceptionHatcher
It’s critical you don’t throw your exceptions too early, they need to learn to fly first 🤣
2 points