Seconding OP, with specific question: When I looked at XSharp a few months back, they were writing about planned support for Mono - which would mean Android. Buuut - that was way back, and in newer posts the topic was not mentioned. In switching I am looking for client side cursor engine - Table, Cursor, Index, Cursoradapter, SQL plus xBase data functions/commands(even if xBase-data not as commands, but methods on some object) would be good enough for me for try, although more syntax equality would be welcome.

Did something along that line crop up ?

>Hi all,
>
>The question is indeed in the title on the thread "Has anyone on UT run tests of the coming XSharp compiler support for VFP syntax?" I can see below on the xsharp forums and website (link below) that the team is working on making sure the VFP syntax is "supported within their dotnet compiler.
>
>https://www.xsharp.info/forum/public-vfp
>
>Of course, lots of questions here including:
>- what is the expected performance of applications built using such a beast,
>- specific performance in terms of data access (VFP is an interpreter but sure we are literally spoiled when massaging data locally within the rushmore indexed cursors - moving a VFP codebase may certainly incur some losses here),
>- what kind of support we can expect when building GUIs.
>
>I understand that SWFox 2019 ran a post-conference training session (link below). Possibly some UT members that may have attended. SWFox in Gilbert was way to far for a continental European to go!. But I'm sure it was an active VFP VFP event. I'd glad we some sort of short) feedback here on this "Xsharp for vfp" introduction.
>
>http://www.swfox.net/workshops.aspx
>
>I am no fan of xbase-syntax compilers. But for sure Robert and the Xsharp team are talking no nonsense here - refreshing in view of the stuff we heard on such matters from MS and a few others - ie on the Xbase syntax in terms of portability into the dotnet world. Yes that's possible (*)
>
>So feedback on X# welcome!
>
>Daniel
>
>(*) PS: Moving the fox out its niche was such made way cheaper with the roslyn technology. A technology possibly not available when the decision to drop vfp was reached. But it looks lke it always was certainly possible to build a dotnet VFP:-) Worth the cost? Possibly not. But well, by the time the decision to drop fox was made, VFP was a robust MS entry in countries that were negligible and that now count. Such as the ex-soviet bloc, Eastern Europe, numerous Asian countries and a few other places that matter a bit to-day.