Tim Uckun wrote: > > > >Finally, one language issue that is a real pet peeve of mine is case > >sensitive variable definitions. This is not a problem in either CFM or ASP. > >While it can be somewhat worked around by setting the PHP error level > >reporting to flag uninitialized variables, it is a deficiency that is long > >overdue to be corrected. > Seeing as how we're having a full fledged 'discussion' about this, I'm going to throw my boot in from a programmers perspective. I know that historically php was Personal Home Page, implying that it was designed for use on personal web sites, not very sophisticated, no security necesary ... just something that was free and easy to use for anyone wanting to make their site a wee bit flasher. That was ten years ago (or therabouts) and like all things it has evolved massively away from the original concept. This evolution is thanks entirely to the efforts of the unpaid developers that see something missing and write a new module, or read lists like this and see what everyone else is having problems - and write a new module to address this. The US and THEM attitude that is becoming prevalent in sectors of this list is not really helpful for anyone - remember that PHP is Open Source - if you want something changing, raise the issue on php.net, or better still do it yourself. If you want a better installer for Windows 9x (if you must use that as a development environment) then write one. Of course there will be niggles, generally caused by different people wanting different things. I guess that that is why the boys at Zend are starting to produce more commercially oriented versions of it, and part of this is to provide what the industry expect as well as home users. Things like case sensitivity in variable names and function names have been prevalent since the early days of all the UNIX variants for workstation or PC. If you have a problem with this sort of thing, then you should probably take a wee step back from coding for a few hours and start a naming convention that you are happy with, and while you're at it (by the way Tim, this is not intended as a dig at you, so please don't take it personally!) just spend a little more time thinking about your programming discipline in general, keep everything consistent - if there's a team of you working on the same app, then make sure that everyone knows the rules... I personally think that case sensitivity in names is very important. I would use it in the absence of overloading, and the same again for classes where I want different constructors to be employed. Be careful when you put in complaints against this sort of thing that you think about the bigger picture - Open Source will only survive if it competes equally with the commercial tools out there. If you remove niceties that 'professional' developers expect, then they will be forced to do the dastardly and buy MS type tools, and the benefits that these guys provide to the Open Source community (like exercising all the codebase a lot harder than homies that just use the basic functionaliy) will instead go to MS! When I get time I'll put together a coherent article to defend php against Larry Seltzer and his buddies,a nd I'll post it here first for review, but until then that's more than enough waffle from me! Tom
-- PHP Windows Mailing List (http://www.php.net/) To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
