Hi Johan,

Thanks for cross-posting the message on the Xsharp forum here. My very best to you and the brilliant X# dev team for 2020!

I'll try to add some input in the coming days. But as an interpreter-based language user, it is always a bit difficult to cross the pond to compiler-based technology. I must admit that I cannot cross the water easily and offer more than what was said already. But I follow up and I'm sure many are who cannot take part of the debate but appreciate the work in progress.

One thing is definitely sure, most VFP-based applications that are still in use - that's a substantial target for sure - have been developped over a long, long period of time, the twenty last years for most of them. And I have to say that what Matt and others have said is true, we tend to use really most of the limited grammatical arsenal that was made available. As far as I am concerned:
- the code for event is often freely distributed, depending on the developper's habits and style, into form-based, procedure-based as well as widget-level event-based procedural code,
- in the latest case, widget-level event-based procedural code, THIS is used when it makes sense,
- extensive subclassing at all levels, including widgets and forms, this really belongs to 2019-aged VFP apps,
- the this and thisform keyworkd are used extensively and they belong to the very heart of my grasp of object-orientation... Of course I do mind when they are called self or whatever.

I understand that it may be quite a challenge to cross the two language universes, compiler-based and interpreter-based xbase technologies! That may take a bit of time:-)

Daniel