>>....
>Have you worked with the Implements keyword? Multi-casting? Delegation design? Composition? (I would also argue that inheritance is used too much by most VFP and Java programmers, and even in those languages the careful use of delegation/composition would create better, less memory-intensive, and more extensible apps. But that's for another board.)
>

Hi Vin;

Marlou actually said "In this case VB sucks" not just "VB sucks". Every language "sucks" at something.

You are right in that we often judge a language by what we have gotten used to. VB has some great features that's lacking in VFP and others. RaiseEvents, multiple interfaces, early binding, etc. But undoubtabley the number one thing that reduces the amount of copy and past and increases code re-usability is inheritance.

We should evaluate languages based on the task we wish to perform. Make your code modular and use VB where it is strong and VFP and others where they are strong.

You mentioned that inheritance could be used too much. I never condidertd that, but you are right, when using a language that supports inheritance we tend to use it to the max, when in some cases our code could be more efficent using delegation.

I have some questions:
1. How does Implements reduce copy and paste?
2. Multi-Casting is such a powerful feature (close inheritance simulation), why do I not see much use of it?
3. What is Composition?