Hi Jim,

OK let me summarize,

1. Your point is that you expect that 95% of VFP developer would expect that the argument in a CASE statement is not going to do any work towards a final process. Only the body of of a CASE should be use for that.

2. As a result of 1, you think that a DO CASE solution is more complex and harder to read for the NEXT developper.

3. As a result of 1 and 2, you believe that this particular use of DO CASE should be outlawed.

My point:

1. I would expect that 90% of all VFP developers not experienced with the use DO CASE constructs where actual work is done, would get used to it very quickly.

2. Though I'll agree that the NEXT programmer has to be more carefull at all DO CASE constructs as he reads them (because you really have to go top down and track what is going on, but that is not really your argument), the other side is that constructs ussually embedded in nested IFs are much easier to read and maintain.

3. As a result of 1 and 2, I think VFP developer should be aware of this kind of DO CASE usages and therefore the usage should be promoted.


We clearly are at the oposing camps.
Cheers,

walter,