>>Thanks. I see potential problems. For instance, A is based on B and C. B has a method that C doesn't, at that time, and A uses that method. Now someone comes along and adds the method to B...and it is something that you'd like a subclass of A to be able to inherit.
>
>Remember, C++ is strongly typed and the binding is very early compared to FoxPro's very late binding. The compiler will detect any conflicts of this sort and notify you immediately. Also, the change will not affect any already compiled classes (at least not until the next compile).

The example should have said "someone comes along and adds the method to C."
Anyways, if you have a class library used in several apps, and you make this change to B and re-compile some applications that don't used B and C together in a class like A, you will not run into any problems. Two months later you re-compile the app with A and you get the error/warning. Hardly immediately. I consider this a potential problem. Don't you?

Joe