Not going to happen.

Besides the functionality of these old commands is intertwined with more modern commands, so that killing them is unlikely to bring much of a size reduction. In many cases all that happened is that syntax changed - functionality was just moved to other commands or functions.

+++ Rick ---

>Ken,
>
>While we're talking runtime size - what are the chances of getting a much "leaner, meaner" runtime library at some point. In partiuclar - I would like to see one that eliminated all the "old" stuff (@says, gets, etc) . Support for 2.x in VFP libraries has to be taking up a chunk. Maybe even split it up into a coup[le libraries, and that way those who need the old stuff could still distribute it.
>
>Ken Matson
>
>>>
>>>How big will the runtime be if it now includes the compiler too?
>>
>>No increase in size. The code that compiles VFP p-code for PRG-->FXP, etc. is part of the language (i.e. COMPILE) and that is part of the runtime already. FoxPro/VFP has always not allowed this. I think it goes back to the days in 1.02/2.0 when the runtime was sold separately and it was feared someone would re-distrubute the runtime with a custom command window, etc.
>>
>>I just checked, and the new runtime is currently 3.3M, exactly 1K less than VFP 6.0. Basically it's the same, no significant change. Keep in mind there is a new part of the runtime, a seperate file called vfp6t.dll for the multi-threaded DLLs, and it's a bit smaller, 3.0M. You will need this file for running multi-threaded DLLs (independent of single threaded DLLs, EXEs, APPs), etc.