Search Results

You have three weaknesses. Your classes should not be aware that they can be created by a factory. Adding them to the factory should cause no change in the class. Instead, you decided they all need a …

You are looking at this from a coding / implementation point of view. That's the wrong view. Ask yourself: What should your application as a whole do if this dependency fails? Can it run successfully? …

Null pointers are the ultimate “fail fast”. Calling your function with a null pointer would be a severe bug in the callers code. So just access the data through this pointer, there is an instant crash …

The switch statement with nine cases is simple, obvious, doesn’t require any extra code, and is easily extended. Note how all the answers actually avoided writing nine cases down. So they are more com …

In C++, a parameter can have type (for example) int i, const int i, int& i, and const int& i. References obviously work different, but if you want to prevent assignment to i, you just make it const in …

You are misunderstanding things. Booleans are there to control code behaviour. What’s bad is calling a method with three arguments f(true, true, false) with no indication what each argument means with …

Nobody cares about whatever table size. But if you create a subclass, then a developer who knows the behaviour of the original class has no clue what your subclass will be doing. A macOS / iOS develop …

You can try writing a plain old function that does 95% of the work, identical for all three classes. And then each class gets a tiny instance method that mostly calls the plain old function. You could …

What makes global state bad is not that it is global, but that basically every single line of code could change the global variable, or could be affected if it is changed. The minimal change in C or C …

You need to pass information from caller to callee. The amount of information can usually not be changed. You can divide this information into lots of primitive parameters, or you can combine some or …

In Objective-C, for a long time observers were not automatically removed from the observable when they got deleted, leading to a crash when the observable sent a notification to an object that didn’t …

In macOS and iOS, intra-app notifications send a name for the notification, and an optional object. Any name, any kind of object. An observer registers for notifications with a certain name, and has t …

Not if it is available to the general public. For example, if you write software for an iPhone, and you just released 1.1.0, Apple won't accept any version 0.x.y, or 1.0.x for your application. If you …

If you have a simple data-only object, declaring and using an interface costs very little. Very often you don’t have a simple data object. Say you have an object that can persist or load itself. Or co …

It depends very much what you mean by singleton. My definition: A “singleton instance” (not class) is an object that serves a specific purpose, that should be exclusively used for that purpose, that i …