> Do you mean the PostgreSQL driver needs to be changed from pg_blah() to > pgBlah() ?
It was that extra underscores having been added to the pg_ functions is being put forward as a reason for adding them everywhere else. That is perhaps when this discussion should have been undertaken, but someone making their prefered driver look how they want is not a good reason for pushing that everywhere else? > If that's the case - why? For procedural API that's totaly fine. As I > said, I think the functions with _ word separator are totaly fine and > it's really no need to change that. Totally agree. > The OO interface, that needs to be build eventually, that one should use > camelCase for all the methods and properties. > This way the code style clearly separates the OO inteface and the > procedural interface. And I think it's good. At least it served me well > all my 10+ years with PHP. We are on the same hymn sheet ... First choice ... leave things alone Ysuo seems intent on 'consistency fixes' though so my second preference if it HAS to happen is simply to reduce the number of underscores > (well, the MySQLi has ->num_rows and stuff - i'd change it to ->numRows and > so forth) as an example of what works better in line with current practice elsewhere? Current RFC is over the top. -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
