Hi Claude,

What JimH is doing is potentially much more exciting: he is making dynamic languages work within the CLR. Applied to VFP, e.g., there would be no interop: it would be managed code. Who knows whether it will be: but if he can do it with Python, then it can be done on VFP, without too many changes.

Hank

>I just wish MS would get behind VFP COM interop with .NET.
>>We have been told, over and over again, that we would lose key functionality in VFP if it were ported to work with the Common Language Runtime, i.e., the CLR, i.e., Visual Studio .NET. This is because the CLR is not made to be used with dynamic languages. Well, guess again: Jim Hunginin (creator of Jython, which is a Java-compatible Python) has been creating IronPython - a fast Python implementation for .NET and Mono, and is now working at Microsoft continuing that work, and helping other dynamic languages integrate with .NET.
>>
>>Frankly, most VFP developers would be pretty happy with Python. Either way, things are looking up for the longterm future of productive software craftsmanship.
>>
>>Hank Fay
>>
>>PS: I can't wait to see the furor this causes; especially the denials from MS (like the denials I had last year about X#, which has now been revealed under another name but with acknowledged roots in a Cambridge Microsoft Research language called, er, X#).