>>I am not saying that VFP is the end-all be-all for OO stuff. Some people insist that because it doesn't have operator overloading or multiple inheritance that it is weaker.
>
>Multiple inheritance was a mistake put into C++, IMHO (the OOP equivalent of spaghetti code). Operator overloading is kind of nice, though.
>
>> I personally do not think mult- inheritance or operator overloading are important.
>
>I could see how both can be viewed as important, I just don't see them as being essential.
>
>> VFP offers a simple syntax for creating objects, supports inheritance, and >packages everything nicely.
>
>And it does what it needs to do, all in OOP fashion. I was amazed when VFP3 came out, and I looked at it and said, "wow, they actually did it right".
Mike,
I couldn't agree more, VFP 3/5/6/7 are easy to use, make sense (oop anyway) ;) and are fast and easily deployed..
jp
User: "Can you make this small cosmetic change"
Programmer: "Just another total rewrite"