On Tuesday 23 March 2004 00:13, Marcus Boerger wrote: > you may consider me responsible for this mess - i must admit i forgot about > sqlite's oo api a long time ago since it is running...(i know lame excuse)
Obviously if we're going for consistency (and I thing we should) sqlite oo iterface should be changed as well. Its now or never, and I think there is still time.
That of course depends on php5 release master. So Andi your thoughts?
I think that being consistent is important and we have almost missed the chance to be so. I am starting to see that people are already using PHP 5 to develop production applications (which are due later this year). In order to minimize the damage caused by changing to studlyCaps, I suggest we make the changes now and roll an RC2 within a week. At least this way, people who are starting to pick-up PHP 5 due to its RC status will not have to change their scripts.
I saw the SQLite patch and I see that a couple of method names have been changed beyond studlyCaps (order was changed), e.g. unbuffered_query -> queryUnbuffered(). The old MySQL extension uses the former so maybe we should stay consistent?
Andi
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
