Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:8723 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 8431 invoked by uid 1010); 23 Mar 2004 23:48:16 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 8407 invoked from network); 23 Mar 2004 23:48:16 -0000 Received: from unknown (HELO shiva.mind.de) (212.42.230.204) by pb1.pair.com with SMTP; 23 Mar 2004 23:48:16 -0000 Received: from [192.168.1.105] (p508EB7BF.dip.t-dialin.net [80.142.183.191]) by shiva.mind.de (Postfix) with ESMTP id 6FF6697B64 for ; Wed, 24 Mar 2004 00:48:16 +0100 (CET) Date: Wed, 24 Mar 2004 00:48:17 +0100 Reply-To: Marcus Boerger X-Priority: 3 (Normal) Message-ID: <198200203812.20040324004817@marcus-boerger.de> To: internals@lists.php.net MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: sqlite's oo api From: helly@php.net (Marcus Boerger) Hello internals, after SQLite's commit ~16hours ago i was reminded that i have violated vertain rules - not change something while in release process and not changing api's of non experimental extensions. I must admit i knew this before but i was in a conflict and i am still. The conflict is i want consistency and there was a decision for studlyCaps. To honor the rules more or less i first contacted the relevant ppl in private and the majority agreed to the change (so i didn't rally wait to hear all). Obviously i was a bit too hastily here. But i only started to workout the change because SQLite's OO API was never released other than in RC1 - and well that it was released like it was is of cause my failure as mentioned already. As you know my actings started a long discussion and now i am questioning: Are we following our rules and decisions? And if so which rule/decision do ppl want me to follow? The one i did which potentially hurts some article writers? Or the other one which would lead to a revert and inconsistency? For the moment my decision is to revert await the outcome of the ongoing discussion. Asked as one of the maintainers i still want the studlyCaps for consistency. Asked for PHP i also want the studlyCaps. It was a big mistake not to change the api right after the decision - as i said my fault. Sorry for the inconvenience Best regards, Marcus The full diff to get SQLite in studlyCaps fashion can be downloaded here: http://marcus-boerger.de/php/ext/sqlite/sqlite-oo-api-studlycaps.diff.txt