>>>If someone created a class with a property named Count, I wouldn't care what kind of results their class gave me ;-) That would probably be the tip of the iceberg as far as unexpected behavior.
>>
>>But it was expected to behave like a collection, before VFP had collections. There were collection classes in frameworks, and they were designed to BE collections - you could call their item() method with number or character key. Which is the expected behavior - of a collection.
>
>I wasn't objecting to creating collection classes before VFP had collections. I was objecting to using a reserved word to name a property of a custom class.

Then Fox team has used a reserved word as a property of a base class later :).

Those troubles are over... but once upon a time, many versions ago, we had a variable named _text, which was used in several places as one to hold accumulated text - a long built string. Then came FP2.0, where _text was the handle of the textmerged file. Search and replace across dozen apps.