Current: $foo->execute_query($query, $param);
I think, current standart is "PHP" standart.
New: $foo->executeQuery($query, $param);
New standart is somethink like DELPHI or C++. Big problem is PHP is
case sensitive. executeQuery and executequery is NOT same. PHP use
another naming convencion as substitute. I think it's better for
users. I choose old standart.
Jan Sun
From: Lukas Smith [mailto:smith@backendmedia.com]
Sent: Tuesday, May 20, 2003 1:04 PMThis is a follow up of a previous thread but this time I will
give it
the RFC label to make it more official:
http://marc.theaimsgroup.com/?l=php-dev&m=105299997308470&w=2I am proposing the use of studlyCaps as the CS standard for object
oriented API's exposed by PHP extensions.I was just informed that I am making this more complex than they
need to
be and that the first thread was enough. I will make the necessary
modifications to the CODING_STANDARDS and will get someone to commit
this.Regards,
Lukas--
====================== REKLAMA =================================
Získajte supervýhodné ADSL ešte výhodnejšie v cenovom odpočítavaní Slovanet
ADSL Teraz! Čím skôr sa rozhodnete, tým viac ušetríte.
http://www.slovanet.sk/menu/adsl.html
Current: $foo->execute_query($query, $param);
I think, current standart is "PHP" standart.New: $foo->executeQuery($query, $param);
New standart is somethink like DELPHI or C++. Big problem is PHP is
case sensitive. executeQuery and executequery is NOT same. PHP use
another naming convencion as substitute. I think it's better for
users. I choose old standart.
Currently the onyl class that is affected is the internal class
"Exception", and that already uses the PEAR standard. (which is the only
OO standard right now). Functional interfaces won't change, nothing else
will changes, we just decide that the way to go for classes in extension
is to use the PEAR OO standard, there is really little to chose for you.
Derick
--
"my other box is your windows PC"
Derick Rethans http://derickrethans.nl/
International PHP Magazine http://php-mag.net/