wv> No, you are not completely right. But you are correct that once a
  wv> function is declared virtual, the function is virtual in all 
  wv> derived classes, and it is not necessary to define it virtual 
  wv> there. I am just used to doing that since often the base class is
  wv> in another module, and so it remembers me not to change the 
  wv> parameterlist. Doing that would hide the original function due to
  wv> function overloading. A lot of compilers give you a warning when 
  wv> that happens, but probably not all :-) 
  wv> 
  wv> If you've got more questions, just ask. 
 
ahhh, good point!  I see where that is useful...  (The book I've been
learning from does not use virtual in the derived classes) 
 
On the off chance that you might know,  do you have any ideas as to what
causes unresolved external errors when using templates?  I've been trying
to use a linked list class and have had such errors all over the place...
what gives?

--- Maximus/2 2.01wb