Using Qt in an application without a GUI, pros and cons?

I am working on a semi-real-time system using C ++. A lot of design and logic is event driven. When searching for any event framework for C ++, I found Qt. The signal / slot, state machine in Qt looks very good for my situation. I prefer them much more than cheering. In addition, the QObject system has many nice features, for example. QObject Model, moc, parent-child object memory management, etc. But I don't know much about Qt, here I have a few questions.

  • Giving me an introduction to C ++ / stl now, is it worth the time to learn Qt? In any case, I will not use its most popular part, UI.

  • What about Qt performance compared to stl / boost? Because the application is live, performance is a key requirement. For example, I have to carefully design the data composition to maximize CPU cache utilization. All the features provided by Qt have some cost. How much can this affect?

  • What about multithreading in Qt development? Can I use a stl or pthread thread with Qt objects or do I need to use the threads provided by Qt? Is it easy to use?

+4
source share
1 answer

Qt , , , Qt, , - STL STL . Qt , .

+6

Source: https://habr.com/ru/post/1523990/


All Articles