Quote:Original post by guyaton
I'm still not fully sure, would you mind a real simple demo?

thanks.

// Public interface class with only pure virtual functions. This is what the users seesclass ITimer {public: virtual int Query() = 0;};// The actual implementation. This is the hidden class that does all of the workclass TimerImpl : public ITimer {private: int Base;public: TimerImpl() { Base = time(NULL); } int Query() { return time(NULL) - Base; }};// And a create function is also exported since the users need a way of creating the hidden TimerImpl'sITimer *CreateTimer() { return new TimerImpl; }

Quote:Original post by guyaton
It was a nice try, however inheriting an Interface apparently makes the inherited class abstract...oh well thanks for the try! where's those microsoft coders? i'm sure they'd solve this in 1/2 a second.

if your curious this is what i did (for anyone else out there who might possess the answer):

*** Source Snippet Removed ***

error is:
error C2259: 'CParserFile' : cannot instantiate abstract class

Quote:Original post by guyaton
thanks! that worked!!!....but i have to do impliment everyting in this other class? doesn't that defeat the purpose of interfaces?

Quote:Original post by guyaton
So pretty much the IParserFile is a placeholder of functions and the class ( CParserFile ) is what holds all the "meat" that the interface does? If this is true, why bother having interfaces then? just to allow compatibility between C and C++??

thanks for all the help thusfar doynax!!