>Al,
>
>>However, if the new approach is to focus on JIT compiling, I see no reason to strip out macro expansion, which is a major benefit to using VFP in the first place.
>
>To do a CLR-capable version, macro expansion would have to go, if the CLR does not support it. I assume it doesn't -- or else why haven't we heard that VB7 or C# will have it?

Look at what a JIT compiler does. You feed it some source code, which it compiles on-the-fly, then runs. Sounds kinda familiar, doesn't it? :-)

Maybe we'll see DEFINE CODEBLOCK and JITCOMPILE commands/directives added to VC++/C#/VB.

You're absolutely right, if macro expansion capabilities aren't in the CLR, then VFP won't have 'em. I just wanted to point out that the bruited underlying technology by no means precludes VFP macro support; in some ways it looks like a "match made in heaven".