>Test coverage for a compiler is one thing: the compiler is fully defined.

ACK, but when it comes to SQL you have side effects based on data and more corner cases.
I found some bugs in vfp9 data engine still, one going back to FPW implementation.

>Test coverage for a large app is an entirely different matter. When you've got 500+ forms, etc., even Java or .Net aren't going to help you. This is not an original thought, btw, it is echoed in multiple language development settings.

Yes, but there are 2 points to it: Dotnet was planned to sport different languages. Even there that worked admirably when the base assumptions were equal, integrating other concepts like IPy, Boo and so on was still mostly roses (using the new languages from C# had some limits) but broke down even more when trying to combine different script languages. Somehow I picture Recital to have more problems, as they cannot match resources.

Second: Having a well defined Fwk for App development will suffer more from those differences - subtle differences in the basic language structure will need to be adressed - unless they transpile always into Javascript or Java before running. Even then, more behaviour to be tested.

And there is still the question, if and to what extent sources are offered: Will have to wait and see until it is released. The trend is to offer sources, as was done with all xBase-parts of vfp, but is perhaps less prevalent in big iron circles.

>
>OTOH, running a web service model does make testing quite easy. With Python, especially, testing is just there, with very little work required to implement and manage it. If Plan A (pyjamas/dabo) doesn't fly for any reason, and Lianja does fly, we would be doing our work in Python (which is to day we will be using Python either way). I have no objection at all to writing in VFP (doing it right now, in fact). And I get additional enjoyment in using Python, much in the same way that eating with dinnerware that matches one's aesthetic taste and functional requirements brings additional pleasure to food.

Yes, I would also prefer to write python with a well designed cursor engine - vfp-xBase has more warts due to age and compatibility and the options found in newer languages give me a better grip on things possible.

regards

thomas