>Hi Ed,
>
>>What is being gained by continuing to support @...SAY...GET in VFP6 - was the support in VFP5 insufficient? Continuing to support all older constructs even when we have new and significantly different language behaviors,and we've provided tools in prior version to port from the old way to the new way of seeing things is adding layers, translations, code and bulk - can you say "Big freaking runtime library?" - and gives both the app developer and the people writing VFP itself more opportunities to miscue in unexpected ways.
>
>With the only problem that VFP 6 is in its core still the old FPW 2.6 product with all the new features added to it. Removing all this stuff would probably mean you have to rewrite major parts of VFP. That's not a bad thing for us, but a big investment for Microsoft...
>

I'd think they already had to do this to already, and it would pay off in spades to have the same basie IDE shared between the itnteractive development tools in Visual Studio.