>I think I have been grossly misunderstood. I said that VFP classes are structures. We never had this before classes. I did not say you can pass them to an API. If you want a structure in VFP that makes it easy to handle an object then just define a class. You don't need any methods.
>

I was just trying to demonstrate that there is a _very_ important difference between a structure and a class, and they are, in no sense of any word, the same thing. A structure is contiguous memory, a class is not (necessarily). I am guessing that you are making this assertion because in some languages the syntax for setting the member of a structure and setting the properties of a class is the same. But that in no way makes a structure the same as a class.

>However the above example can still be done in VFP. You have to create the "structure" as a 20 char string. Then parse the result it in 4 byte increments making sure you reverse the double words appropriately using the Intel format.
>

I know we can do structures in VFP. The reason that we have to create a 20 byte string is that a string is a necessarily contiguous piece of memory.

I think that this debate goes beyond arguing semantics, and crosses the boundary into arguing the sheer misuse of the word.

my .02