You're 100% right, I think it's one of VFP's few downsides. I wish there was a way to *enforce* case sensitivity with variables in VFP (consistency is a good thing).
To some extent, perhaps I'd even like to see strict data typing, although I wouldn't want to lose macro expansion and other cool tricks as a result. Whenever I spend lots of time working in C/C++, and switch back to VFP, and see my all my unintentional inconsistencies with case, and who knows about data typing mistakes, it makes me shudder. It's the only major limitation in my mind of VFP, but then again, I'm willing to bet most other VFP coders probably see it as a big advantage. I just wish there was an option to support both ways. >Oh, I forgot to mention the main reason I like case-sensitivity in >general: It >doesn't let you get sloppy. I look back at my VFP code today, code I >was proud of, >and I can't believe how inconsistent I was in whitespace and casing. >Things like: > >IF ... > ... > ... >else > ... > ... >endif > >and calling it m.CustomerName in one place and m.customername in another. > >Case-sensitivity simply doesn't allow for this unforgivable >sloppiness, so the >sloppiness doesn't happen in the first place. > >I think the same argument could be made for files in a filesystem. >Being sloppy with >naming will result in problems. > >Paul _______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/20090326173705.968f298...@marge.leafe.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
