rmed

Recently I've had to tackle the task of making two different software architectures, a modern one and a legacy one (as it happens), work together in C++. These two architectures were based on two completely different event-based frameworks, each one with their own event loop, and it was clear that they were not intended to work toegether as one, but rather assume that they are completely isolated components that handle the entire application lifecycle.

Python has lots of libraries available for almost anything imaginable. However, there are times when, for one reason or another, you need to use native code written in C/C++ (e.g. legacy code, hard requirement for a specific project, etc.). Although there are several options to overcome this need, we are going to have a look at SWIG.