>>But changing such a central part plus all the planned additions: perhaps starting from a clean slate
>>with a new language might be cleaner.
>>Getting users to adopt a totally new language: oodles more difficult, so perhaps less changes and
>>getting a running version while a few reamining vfp devs still want one might be more important,
>>which was the background for my "shipping is a feature" ;-)
>
>
>Do people use PRIVATE? I've never used it in my entire VFP career. I don't mind adding support in there if it's required. But if only a few people use it, there are better ways to code.
>
>I see no purpose or benefit to keeping it. Perhaps you can explain it to me.

I use private memvars when I need to pass them in a SQL pass through command, like "Update sometable set field1=10 where myfield = ?pcVvalue". I was told that it's the best way, and sometimes necessary. I never questioned what I was told.