Warp wrote:
> Darren New <dne### [at] sanrrcom> wrote:
>> I don't know. I've seen it happen at runtime with "trying to invoke pure 
>> virtual function" on Windows, and now I'm getting some of the same sorts of 
>> messages from a Linux program (from a place where you're supposed to fill in 
>> as you port it, so not entirely unexpected).
> 
>   That runtime error can happen when you call a pure virtual function from
> the base class constructor (even if the object being instantiated is not
> abstract).

Yeah, but that would happen even if the child object implemented the 
function, yes?  In other words, this wouldn't be a bug of "you didn't 
implement the child correctly", but rather a bug that would persist even 
after the child object was correct?

Anyway, I'll be delving into this part of it pretty soon. Basically, as soon 
as I've groped thru the hardware docs to see how I have to port the stuff. 
I'll let youknow if I figure out what C++ is triggering this and how it 
manages to compile.

(I do get some compile-time warnings, but they're mostly things like unused 
member variables and switch statements that don't cover the entire 
enumeration and such. Nothing at link time and nothing about abstract classes.)

-- 
   Darren New, San Diego CA, USA (PST)
   There's no CD like OCD, there's no CD I knoooow!

Post a reply to this message