Thanx for your time Eskimo, I am taking a class on data structures using C++ (I love it jeje) We havent talked about abstract classes yet, but I was doing a little reading ahead and I bumped into this part about pure virtual functions (they divide virtual functions in three areas, basically the ones you have to make virtual, because like I said u used the same one for differente classes and in running time the program has to make a difference to what object it is being called for, the ones that you may or may not declare as virtual, cause maybe u think someone (or you) can make a derived class from yours and use the same function thats also in the base class, and the pure virtual classes that are exclusive to abstract classes (u equal them to cero by the way jeje)) anyways i kinda lost myself there, the compilers dont give me warning everytime, it depends on what the function is. In the case of the pure virtual one I tried it didnt give me a warning when I just put the headings and leave the implementation blank. I guess youre right about not taking virtual functions into derived classes that dont do nothing

By the way sorry if i cant make myself really clear but english is not my first language. Spanish is, from Puerto Rico

thanx again bye byee