Hi Jim,

From what I understand, the VFP code base still has all the Unix code in addition to the Mac stuff. While I agree with what you are saying with respect to the current subject, I fail to see where the removal of code supporting these platforms sacrifices backward compatibility. If anything, the VFP runtime will be substantially trimmed down - this would benefit VFP in many ways (particularly with COM).

While this would not be considered a "new feature", I think it's an important issue for the FoxTeam to address - the "bloat" issue.

This is one of my top-ten wish list items.



>The history is important in understanding why the VFP controls are as they are, FP 2.X was originally multiplatform supporting DOS, Win, Mac, and Unix. The source code was compatible for all platforms. In order to do that Fox had to control the screen display so it could handle things differently on different platforms.
>
>VFP 3.0 was for Win and Mac, and the same issues applied. The controls became instrumental to the internals of the product. We got a bunch of events and methods that the windows controls don't have. A real lot of code has been written that depends on the events and methods being there and using the inherent data binding capabilities of the controls.
>
>To change these features now would sacrifice backward compatibility of code. That may not be bad thing, but it certainly isn't something to be taken lightly.