Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Why not POCO (Plain Old C++ Object)?

object plain Poco
0
Posted

Why not POCO (Plain Old C++ Object)?

0

Short answer is that I don’t know how to do that. As C++ does not provide reflection information, there’s no way to load a library and find out what’s in there unless some information were manually inserted. The downside is that we have to define the objects Qt way. But we got the information we need. Is it intrusive? Yes and No. Yes. We cannot just use any c++ objects. No, because we can still use the objects in other Qt applications without linking to QtIOCContainer. In this sense, the objects are POQO (Plain Old Qt Object). The other alternative is to use a C++ reflection library (e.g. SEAL Reflex Library) to do the same thing. It might be a better solution. But I guess the components have to be linked in the application and no longer pluggable.

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123