Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:124846
Date: Sun, 11 Aug 2024 11:37:43 +0000
To: "Christoph M. Becker" <cmbecker69@gmx.de>
Cc: PHP internals <internals@lists.php.net>
Subject: Re: [PHP-DEV] PDO_Firebird: use C++?
Message-ID: <AHoY5EYa569C28qIB2vpoTB29TCFe1fS-KmN5VzgR8tRXNcHQhNzv7Hf_28zfIK4HapHUwowleez1sF2HxLoukHZLWKIr6VzPNLeyGw_9RA=@gpb.moe>
In-Reply-To: <ed3adfd7-a13e-4bcb-9390-2ccf057a651d@gmx.de>
References: <ed3adfd7-a13e-4bcb-9390-2ccf057a651d@gmx.de>
Feedback-ID: 96993444:user:proton
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: internals@gpb.moe ("Gina P. Banyard")

On Saturday, 10 August 2024 at 15:13, Christoph M. Becker <cmbecker69@gmx.d=
e> wrote:

> Hi all,
>=20
> a week ago Denis Simonov submitted a PR[1] regarding formatting of the
> new time zone types of Firebird 4.0 (which appears sensible per se).
> This requires to access new Firebird APIs which are written in C++ (the
> old Interbase APIs are still provided as C code). Now the Firebird
> developers have written a tool for cross language support called
> CLOOP[2] which allows to access the APIs written in C++ directly from C.
> However, they do not provide these C APIs officially, so Denis provided
> the minimal required C API for inclusion into the PDO_Firebird extension[=
3].
>=20
> In my opinion, this a somewhat fragile approach (especially since
> CLOOP's C generator apparently hasn't been tested for a rather long
> time[4]) and would personally rather use C++ to access the new APIs.
> This would obviously require a C++ compiler to build PDO_Firebird (so
> far a C compiler is sufficient), unless the C++ code (and the respective
> functionality) would be optional.
>=20
> Another drawback would affect the Windows builds; so far these just
> could use the Firebird kits provided by the Firebird developers (which
> contain headers and pre-built libraries), but these don't contain any
> C++ libraries, so the libraries would need to be built and hosted by
> winlibs[5] (at least for the time being).
>=20
> I assume, however, that (Linux) distros already provide pre-built C++
> libraries since the new Firebird OO API is available as of Firebird 3.0.
> Maybe someone can confirm that.
>=20
> So what do you think? Should we use C++ to access the new APIs, or
> stick with C (and include the required declarations in PDO_Firebird)?
>=20
> [1] https://github.com/php/php-src/pull/15230
>=20
> [2]
> https://www.firebirdnews.org/new-firebird-interface-cloop-cross-language-=
object-oriented-programming/
>=20
> [3]
> https://github.com/php/php-src/pull/15230/files#diff-e0657e20b6fc2c130f50=
4c18ebeeac828847f17f1f8f7c3559b8fe8b2bc19928
>=20
> [4] https://github.com/FirebirdSQL/firebird/issues/8197
>=20
> [5] https://github.com/winlibs
>=20
>=20
> Cheers,
> Christoph

I think moving the PDO driver to use C++ is a more sensible choice.

Best regards,

Gina P. Banyard