Re: anti-advocacy: Larry Seltzer, pcmag May'01 pub.

Hi Theo: <also not a flame> It's interesting - I look at it like: is there any reason why you'd want a StrPos(), Strpos(), etc. functions that do different things? Actually I certainly always try to type things the same way, but if I accidentally type Strpos instead of StrPos, I don't want to have that generate an error. I follow a variable/function naming (and case) convention in both PHP & other languages (all constants are UPPER_CASE for example). I agree that this can help people understand the code, but this convention works just as well in a case-insensitive language. Actually, one thing that I REALLY like about the newer VB development environment is that it will automatically correct/adjust the case of your variables/functions to match their definition. This allows me to define them according to my naming convention, but not have to worry about keeping them straight in the code - the tool handles it for me & that's as it should be. Since I use HomeSite for editing my PHP code (& ASP too), I don't get that benefit. </also not a flame> -- Greg ""Brinkman, Theodore"" <Theodore.Brinkman@standardregister.com> wrote in message news:FE8510398BFE854F9653B5C32DBB652FD4F397@oh_daytn_xch01... > <not a flame> > > Hey! Some of us out here LIKE case-sensitive languages. Is there really > any reason why you need to use STRPOS() in one place, StrPos() in another, > Strpos() in another, and strpos() in another? If you use any sort of naming > convention, the case-sensitivity actually HELPS people understand your code. > > Get used to it, even html is going to end up being case sensitive when xhtml > becomes the day-to-day standard. > > </not a flame> > > - Theo