>>Yes but it is in VFP. ;-) This has been on my list for some time but I'm not sure if it will be implemented. The reason I think this (and this is all conjecture on my part) is that VFP uses variant data types. As such there is no "limit" on the amount of information that can be stored in a variable (beyond the limits mentioned in all VFP variables). Structures are finite contiguous blocks of memory. How can you define a finite block of memory when everything in it is variant? You can't. VFP would have to have true "strong typing" and this, I believe, would break so many applications that you could hear the screams from the moon. < s >
>
>I think there is nothing inherently wrong with strong typing. It could be implemented as optional: say, if your program includes: "#DEFINE STRONGTYPING .T.", or SET STRONGTYPING ON, it would be enforced. Otherwise, it wouldn't. Default: compatibility. See: SET STRICTDATE.

I personally don't think it could be done as a setting. I think it would have to be done using another run-time library (the way they had to go when implementing multi-threading). Having it in the development environment would also entail a new set of DLLs.

A setting is a flag that is evaluated when it needs to be. It doesn't affect the underlying storage. This would. The memory management functions would need to be revamped and this is something that would take a large percentage of the Fox team's resources (IMO).

Mind you, this is all guessing on my part. However, if I am correct, it doesn't provide enough "bang for the buck" (quoted from Randy Brown in another thread). You can do this stuff in VB and VC++. Or you can access the same functionality using a number of COM wrappers already implemented by MS.

While I would like to see it, I just don't see it as a requirement.