>>>I would like to use mixed case method and property names. Why does VFP insist making them lower case? Is there some innane reason?
>>
>>Inane? Dunno as the quality of the reason. It just is. Perhaps it's because Fox isn't case sensitive, which most people would probably agree is a good thing. But, really, it's just so. FWIW, that is one kinda silly reason I like programmatic classes. Completely non-functional reason, but it suits my esthetics, too.
>
>Is inane a word? Maybe I meant insane :). Actually its more than esthetics at stake. Readability of code is a big factor. Take a method name example this.atPutAll(object) vs. this.atputall(object). And anyway, the built in methods and properties are in mixed case. So why should my additional ones be any different.
>
>>>>Also when I create a property in why can't I initialize it from the properties window?
>>
>>Do you mean from the define properties window? That would be convenient. Make a wish for 8.0?
>
>Hey there is a name for 8.0? The Genie. This way we can all get our wishes.
>
>costas


yeah, 'inane' is a word, it means 'silly' or 'asinine'. which to use,
inane or asinine ? depends who you're talking to and what you think
of them ;)

completely agree with you that capitalization in names is preferable.
i note you don't use underscores in your names, which i find improves
readability a lot too. also, i prefer built-ins typed in all
UPPERCASE.

just because VFP decapitates your names in PEM list, doesn't keep
you from writing them in that style in your code.

here's a wish list item for you Genie too ... if i change the spelling
of a user-defined property or method, let the VFP IDE find all occurences
in the code and update, possibly with confirmation. something like that
would save me a lot more time than 'code completion'.