Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:40960 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 23954 invoked from network); 13 Oct 2008 23:13:50 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 13 Oct 2008 23:13:50 -0000 Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass; domainkeys=bad Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.198.237 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: pierre.php@gmail.com X-Host-Fingerprint: 209.85.198.237 rv-out-0506.google.com Received: from [209.85.198.237] ([209.85.198.237:25089] helo=rv-out-0506.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id EE/46-36838-D26D3F84 for ; Mon, 13 Oct 2008 19:13:50 -0400 Received: by rv-out-0506.google.com with SMTP id g37so2173619rvb.23 for ; Mon, 13 Oct 2008 16:13:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=L1n+Izwljk/EWdYLK3s7lU8H41Zl9ZPlGS6of/TCwBI=; b=OiDJFtFtR3s3o5gbtlYw34wESuWuZfIHKYPayr8wcrjjBx1rwkfs+PLw6cDUm5srdk pcBM2e5H3qI9HziKnUZV9fgqpdCjGa34J5ZMOUCtC7I3DFwVdTW09AyTe1crlcj0FsmF rH2qGsZ6bHUI8kjZDsw8uxe2Haac5UM3WQyq4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=nsEEEjOs+QCo/FcypIscRcxZU6Nuts27rqG7vUXbLKoq3wDPngOeOz3/4wrb3XIC7A XitvABdx8qUCDc2rMJXRlR3FzZO8ZNtBhvVNWW3Ifej1Z5tyRZMKNsApuu4v+oHgT12V KtVF6gb/FrICbA6RqJVdqHpxKL+iV6BhVmoPE= Received: by 10.141.162.9 with SMTP id p9mr4289678rvo.68.1223939626995; Mon, 13 Oct 2008 16:13:46 -0700 (PDT) Received: by 10.140.178.14 with HTTP; Mon, 13 Oct 2008 16:13:46 -0700 (PDT) Message-ID: Date: Tue, 14 Oct 2008 01:13:46 +0200 To: "Jochem Maas" Cc: "Lukas Kahwe Smith" , "Lester Caine" , internals@lists.php.net In-Reply-To: <48F3D13F.70801@iamjochem.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <48EBA7E4.7060305@lsces.co.uk> <5E0F8553-2F2C-448D-936D-B39517F661BF@pooteeweet.org> <48F3D13F.70801@iamjochem.com> Subject: Re: [PHP-DEV] php_firebird From: pierre.php@gmail.com ("Pierre Joye") Hi On Tue, Oct 14, 2008 at 12:52 AM, Jochem Maas wrote: > Lukas Kahwe Smith schreef: >> >> On 07.10.2008, at 20:18, Lester Caine wrote: >> >>> What is the correct procedure to create a new driver, or rather clone >>> the existing php_interbase so that we can build a proper Firebird >>> version that actually uses the fbclient.dll rather than sharing the >>> now incompatible GDS32.DLL client. Some people are starting to use >>> Interbase in parallel with Firebird, but the driver can only access >>> one client :( > > not that I give a **** about the windows interbase/firebird extension .. but .. When will you (all) understand that it is not only a windows problem? The fact that windows is likely to do not have it in 5.3 is only a side effect of the lack of developers around this extension (zero developer). And seriously, comments like that do not have their place in this list. I could say the same about firebird and simply keep away from the windows releases and let the firebird users deal with that. > I do use firebird and all this talk of dropping firebird support is kind of scary > (well really scary actually) ... I am able to configure php with '--with-interbase' > in 5.3alpha2 so I guess I don't need to worry. We are not talking about abandon it but moving out of core. Please note that it will not happen tomorrow (5.3). But if nothing changes, I do not see how this extension could remain in core without maintainers, but that's not something I can decide on my own or for 5.3 :) I find amazing that so many users are scary about loosing firebird in core (they can always install it via pecl then) but I do not see too much love around it (unit tests, bugs reports, patches, attempt to contact the firebird developers, etc.). > effectively the extension for firebird already exists ... it just maps to the interbase > function, if the fbird_*() aliases were removed and renamed copies the ibase_*() > extensions functions created that then were built against the firebird client iso > the interbase client you'd pretty much be there. technically the [firebird] extension > would be new but is that really a deal breaker given that the complete API (fbird_*()) > already exists? I do not understand this paragraph. > PS - I've been trying to follow these firebird shannanigans but it's all been > a little too UPPER CASE for me to grok. :-/ Agreed :) Cheers, -- Pierre http://blog.thepimp.net | http://www.libgd.org