[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Openparts and "virtual"
From:       <dsweet () chaos ! umd ! edu>
Date:       1999-07-03 2:38:32
[Download RAW message or body]

Ok...never mind.  

Here are the answers if you're interested

	1) "virtual" here means that the class you're deriving from is
	abstract (i.e., it has methods declared like
		virtual whatever1 somemethod (whatever2) = 0; )
	2) There really was no problem here.  I just accidentally tried
to use "new" on the abstract MyPart class created by the MICO idl.  I
meant to use it on the class I derived from MyPart_skel.  

Dave


On Fri, 2 Jul 1999 dsweet@chaos.umd.edu wrote:

> I have two (possibly related) questions:
> 	1) What does "virtual" mean when you subclass like this:
> 		class MyClass : virtual public TheirClass { ...
> 
> 	2) When I try to compile a test program which embeds an
> OPPart in a MainWindow I get (I've made a stripped-down example
> for myself from the code in embed2):
> 	myopapp.cpp:59: cannot allocate an object of type
> `::MyModule::MyPart' 
> 	myopapp.cpp:59:  since the following virtual
> functions are abstract: 
> 	myopapp.cpp:59:  void ::KOM::Base::connect(const
> char *, class ::KOM::Base *, const char *) 
> 	myopapp.cpp:59:  void ::KOM::Base::disconnect(const char *, class
> ::KOM::Base *, const char *)
> 
> 	and the list goes on and on.
> 
> Thanks for the help so far and TIA for more!
> 
> Dave
> 
> 
> 

[prev in list] [next in list] [prev in thread] [next in thread]