[Snip...]
>
>I'm not suggesting getting rid of the Xbase commands, I in fact like them a great deal for their power and flexibility. They provide many things that other languages don't (e.g. VB). But I do think they could possibly be rejiggered to follow the standard dot notation that VFP itself has in newer language elements. This would probably lessen the learning curve for new developers and condition everyone to think along the line of objects and object hierarchies. Take a look at my original message to see the list of suggestions. I thought these recommendations might give more organization to the language. With this structure, one only has to use a tool like Ken Levy's excellent Superclass to get at things like _vfp.application.arrays.*** for a complete list of array commands and functions. This is much easier than going into the online docs every time you want to see all the commands for array manipulation. This morphing of XBASE commands into object groups would be a valuable next
>step in the evolution of VFP.

Ryan,

I am going to have to disagree with you... at least partially. The existing command structure cannot be changed like that inasmuch as it would break too much code. The objects and new syntax you are advocating *could* be added.

A long time ago I suggested moving the old commands out to a separate .DLL and only bringing it in when needed. That would reduce some of the memory bloat. MS may have taken care of that with the way they load their functions... I don't know.