Hi Matus, Just to clarify that my reflection does not need to make any assumption about the reflected class, i.e. inherited from any virtual base class (interface) or not, and the reflection API do not need to know anything about the reflected class definition or its base interface class if any. So you can see that the main program in my example does not include any compile-time information about the reflected class. And the shared library does not export any symbol (in fact the registration just happens when you dlopen that library). Regards, JinHua 2011/12/7 jinhua luo <ljh.home.king@gmail.com>
Hi Matus,
Could you write some codes to implement the same example I showed in my first mail? That is, define a concrete class in the shared library, and declare/register it there, while the main program just dynamically loads the shared library (note that do not need any initialization, just dlopen is enough, do not need any symbol exported there and be loaded via dlsym), reflects the class, invoke its methods, access its members.
Then we can have more clear comparison regarding the same context between two libraries.
Regards, JinHua