>
> > This sound you forgot to provide an implementation of some virtual method of
> > your TestHeader class (destructor for example).
> > To reply your question one needs that class implementation file.
> > That you did not send us yet.
>
> Ok, I'm embarrassed :)
> Thanks!
>
> By the way, is it typical for a compiler to let you get away with such
> actions?
Hello, Mike.
It is not compiler. The compiler alone has no way to recognize the problem.
One defines the class interface with a single *.h file. Then one provides the implementation.
The implementation can be provided with several files. So even the compiler may realize some
particular implementation file lacks of the method implementation it says nothing. This method
implementation may come from elsewhere.
When you load the share library all undefined references must be delivered It is loader it realizes there is no
some method implementation and it does say about that. The problem is sometime the loader can recognize
one lacks of SOME method but can not say which one exactly due multiply inheritance.
Hope this helps.
Valeri
>
> mike
>
> ///////////////////////////////////////////////////////////////////
> // Graduate Research Assistant // High Energy Physics //
> // RLM Office: (512) 471-8426 // University of Texas, Austin //
> // RLM Lab: (512) 471-3526 // kordosky@hep.utexas.edu //
> // ENS Lab: (512) 475-8673 // kordosky@fnal.gov //
> ///////////////////////////////////////////////////////////////////
>
>
This archive was generated by hypermail 2b29 : Tue Jan 01 2002 - 17:50:50 MET