Since the previous October snapshot Magnum gained Visual Studio port, font conversion utility, improved text rendering along with example application, support for OpenGL debug output, documentation updates, better test coverage and many more usability improvements and fixes.
Large C++ projects often suffer with very long times for both full and incremental compilation, severely hurting productivity. The following series will overview some techniques employed in Magnum to make iteration times smaller, this article focuses on code-based optimizations.
Summary of changes during the first two months after public release. Two new ports, usability improvements, OpenGL limit queries and introduction of API deprecation.
Thanks to generic programming and other features exclusive to C++ it is possible to handle polymorphism the most effective way for each use case. As a result, virtual calls are in Magnum used very sparingly.
While the previous part was focused on C++11 features improving performance, here I will describe features which are used just to simplify your life by writing more concise code with less mistakes.
Regardless to what language you use, you always need to think about memory management. Garbage collectors might give you a sense that it’s done automagically, but to get more performance you need to have control over heap usage in code running at 60 FPS. C++11 helps to avoid many heap allocations without sacrificing usability.
After nearly three years of semi-public hyperactive development, I think it’s the time to release this beast into wild. Say hello to Magnum, modular graphics engine written in C++11 and OpenGL.
Originally developed for Kompas, this library provides both static and dynamic plugin management with dependency support and also various filesystem, portability and debugging utilities.