Re: Resurrecting the Function Renaming Thread

From: Date: Wed, 07 Feb 2001 15:58:21 +0000
Subject: Re: Resurrecting the Function Renaming Thread
References: 1 2  Groups: php.qa 
Request: Send a blank email to php-qa+get-2282@lists.php.net to get a copy of this message
On Wed, 07 Feb 2001, James Moore wrote: > This is true but it sure as hell makes understanding C code easier, If you > are familiar with PHP then look at C code you can at least get the general > gist of whats going on (ignoring structs and pointers etc) and there is a > lot to be said for this, anyway you sure as hell wont get all developers > agreeing to depreciate old names and introduce hundreds of new names into > the name space. Start with a clean up and YES alias with systematic names > but I sure as hell do not want to have to relearn hundreds of function > names, its bad enough atm when I hack in C I find myself using PHP syntax > and function names and vica versa. DONT SCREW UP WHAT WORKS, and dont give > options for people to disable old function names, I want to know my current > scripts will work on ALL versions of PHP not just some. James is right.. PHP was never designed and implemented in a clean room by a single person (unlike Python) - it's a glue language that's been evolving according to what its users wanted to take from and give to it. That said, standardizing function names seems like a good idea - but it will only help newcomers - experienced PHP coders will not benefit from this change. We also have to take into account the pros and cons of this change - once it's done we will suddenly have strlen() _and_ str_len() and newcomers may be confused... -Andrei 'Any given program, when running correctly, is obsolete.' - First Law of Computer Programming

« previous php.qa (#2282) next »