[Somelib] Trying to grasp what the processes are for creating a SOME object

[John P. <jo...@ma...>]

I was going over the code and I am getting a bit confused on how it
creates an object.  One sticking point is the Info class.  What exactly
is the code doing?  It looks a bit non-standard and I want to keep the
implementation of SOMEObjects as easy as implementing standard C++
objects.  If this means putting the burden of complexety on the SOMELib
side then so be it.  Better to have the library be complicated once
instead of the objects being complicated every time you want to create a
new one.  Perhaps I am just tired and I am just not seeing the
simplicity in design here (I did have two tests today).  What I want is
to be able to create an object foo such as:

class foo():public foo_interface{
    foo();
    ...
    virtual std:string doFoo();
    ...
    etc.
}

And then be able to load and use it:

foo_interfaces foo_obj = somehow_get_a_ref_to_foo();
std:cout<<foo_obj->doFoo()<<std:endl;

While having an info class for dynamic intefaces is great it unneedingly
complicates the static plugin interfaces which don't change.  Is there a
way to create objects without the info classes and save the info class
for when we implement dynamic interfaces?  Or am I just missing the
whole point of the info class?

-Quinticent