>>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.