Invisible wrote:
> We have a buggy program that keeps throwing exceptions due to a "pure 
> virtual function call".

Usually that means you're invoking a dynamically-bound method for which 
there is no definition. I didn't know you could get that in C++ as the 
first mistake the program makes.

-- 
   Darren New / San Diego, CA, USA (PST)
     Remember the good old days, when we
     used to complain about cryptography
     being export-restricted?

Post a reply to this message