Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:74222 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 57059 invoked from network); 15 May 2014 11:32:49 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 15 May 2014 11:32:49 -0000 Authentication-Results: pb1.pair.com header.from=johannes@schlueters.de; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=johannes@schlueters.de; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain schlueters.de from 217.114.215.10 cause and error) X-PHP-List-Original-Sender: johannes@schlueters.de X-Host-Fingerprint: 217.114.215.10 mail.experimentalworks.net Received: from [217.114.215.10] ([217.114.215.10:46024] helo=mail.experimentalworks.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id F5/95-14382-FD5A4735 for ; Thu, 15 May 2014 07:32:48 -0400 Received: from [192.168.2.31] (ppp-93-104-0-129.dynamic.mnet-online.de [93.104.0.129]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: johannes@schlueters.de) by mail.experimentalworks.net (Postfix) with ESMTPSA id EC9C742938; Thu, 15 May 2014 13:33:41 +0200 (CEST) To: Lester Caine Cc: PHP internals In-Reply-To: <53747494.2000807@lsces.co.uk> References: <53747494.2000807@lsces.co.uk> Content-Type: text/plain; charset="UTF-8" Date: Thu, 15 May 2014 13:32:24 +0200 Message-ID: <1400153545.2663.1405.camel@guybrush> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Support for all users? From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=) On Thu, 2014-05-15 at 09:02 +0100, Lester Caine wrote: > Having now established that phpng only currently supports MySQL and > SQLite, many of us are once again cut out of the loop. That the > structural changes require a deep understanding of the 'new engine' to > make the missing extensions available cuts out other people picking up > the baton easily, so we are stuck with a half built alternative and no > roadmap as to when it may be testable by everyone? Well, the changes most extensions need for ng are mostly straight-forward, mostly mechanical and probably we can even automate that to quite some degree (be it with some grep/sed/... foo or a clan plugin) But even then the actual issue remains: We don't have developers who know how to setup all libraries and systems to test those changes. PHP, for the most part, is driven by people who have a problem and work on it. Looking at the history of the interbase extension it is more than 10 years since anything but mechanical changes have been made. If you provide constructive feedback and test those mechanical changes I'm sure somebody will assist ... but best is if you find somebody from the firebird community who wants to work on this, I'm sure they'd be welcomed ... johannes