On 10-Feb-2017 3:16 PM, Alan Bourke wrote:
Add to that the source code for the VFP extensions for C# /VB .NET and I can see where these guys are coming from, and maybe where they're going
Yeas, I hadn't realised that Clipper/Visual Objects had that extensibility. They've commented that you could implement quite a few VFP functions that way. To me however the Clipper world is sufficiently syntactically different that the best way is just to implement a new Antlr grammar for VFP code in the same way that they already have for X#.
Alan, it's been a *very* long time and a lot of beer has flowed, but from memory the big syntactic differences were Browse and array handling (Clipper's was much better than FoxPro's - iirc a Clipper array is implemented as a pointer to a list, each entry can be any sort of value including an array). Forms and reports are also different, but I suspect that there would be problems implementing those (and the FoxPro "Window") in .Net anyway. Thinking laterally, someone (Christoff?) was said to be working on a new intercode parser, which might be on similar lines, or even to generate ECMAscript from VFP syntax?