If I (have to) use C/C++, I'm mostly working on time-critical or real-time applications. Examples are OpenGL texture Streaming (Example: Streaming Satalite Data on planet surface in realtime: https://www.youtube.com/watch?v=ws2ra5MvDi4) or real-time PSM audio maonpulation (Example: Automatic tuning a guitar to a C64= SID tremolo: http://www.yousry.de/audio-example-real-time-tune-detection-tuning-auto-tuning/).
During development I'm using "-O0 -g" as compiler options to enable dwarf debugging information.
But as result, STL becomes unusable slow (missing loop unroling, vec optimizations etc.)
In these cases I write code like:
#ifndef DEBUG // deque too slow std::deque<float> inFIFO; std::deque<float> outFIFO; #else float* inFIFO; float* outFIFO; #endif
to avoid later discussions "Why I still use shi##y C and not that wonderfull C++"
This otherwise results in ugly, badly readable source-code. Does an workaround exists I'm not aware of, to efficently use the STL in an development environment?