>>In the pre-VFP days, there were people who used DO WHILE .T. as a wrapper around many routines. I've inherited a couple of applications where most of the code does that. I think it was bad style in FP2.x days and I think it's bad style now. (It might have been reasonable in the days before the foundation READ.)

Agreed for VFP but for VFP C++ Compiler, wrapping in DO WHILE adds another layer of headache for hackers. Not that everybody cares, but it's low cost especially if already present.

Perhaps a new meaning for 'what goes around comes around"? ;-)

I will throw my hat in the ring to give a talk specifically on VFP C++ Compiler touching on this along with encryption compression security etc

On the topic of encryption: when Craig Boyd did his vfpencryption.fll, AES ECB was a default encryption standard, but hack vectors have been confirmed since then so that some customers and jurisdictions now disallow ECB. Craig's fll allows other standards like CBC that work well and do not have the attack vector. It requires one parameter change plus an extra parameter so I'd recommend people start looking at that now rather than waiting for a customer to query.