Search Results

As so often, it depends. If your two decoders decode the same format with slight variations (example: different versions of the same format, or maybe XML with or without character entities), then it …

At some point, some C++ standard libraries contained specializations of the containers for any T*, making them thin wrappers around containers of void*. This was done to reduce generated code duplica …

When you want to represent distinct concepts, you should create separate types. Yes, this may come with some boilerplate for operator overloading, but having distinct types may offer significant advan …

Richard's comment is most of the answer already. Whenever you're programming for anything but a class exercise, you'll want to reuse as much existing code as possible, with just a few other considerat …

It's easy to prevent the verbosity of calling C functions from cluttering your code: wrap them. In the case of recv, for example, you can simply do this: template <typename T> ssize_t recv(int fd, T& …

Yes, Factory is the right name for this pattern. No, C++ does not offer a way to enumerate types. You can perhaps reduce the necessary boilerplate with some clever macros, but I would not suggest it. …

Classes define behavior. If your Garfield and Snoopy don't have different behavior from other cats and dogs, they should most definitely not have their own class. Consider whether you can't just creat …

An exception that you catch gives you the opportunity to print a nice error message or even try to recover from the error (possibly by just re-launching the application). However, in C++ an exception …

Returning something if that something is there, and nothing otherwise, is exactly what std::optional is made for. If your compiler doesn't yet have this type and you can't upgrade, you can use the Bo …

Yes, and it's unnecessary too. You can declare constants in headers and define them in source files just like functions: class AppConstants { public: static const int Max; static const std::strin …

It gets interesting when Run does other things besides just calling DoIt, and DoIt is just a customization point. So basically,Run is a complicated operation, with small variations. Those variations a …

A class's interface needs to protect its internal state so that its invariants cannot be violated by outside users. (Within reason, of course. C++ makes it impossible to protect against all modificati …

There are two concerns here: Is there a use-after-free? You need to ensure that the class instance survives long enough for the thread to finish. C++ will generally not help you here, but you could, …

Yes, though some coding standards may prohibit it. Yes. The recommended way is to throw an exception. Alternatively, you can store the error information inside the object and provide methods to acces …

You can use C++20 concepts to add an assertion that your platform mutex really fulfills the requirements. #include <type_traits> //#include "platform/Mutex.hpp" class Mutex { public: void lock() …