Re: PDO_Firebird: use C++?

From: Date: Sun, 11 Aug 2024 17:05:28 +0000
Subject: Re: PDO_Firebird: use C++?
References: 1 2 3 4  Groups: php.internals 
Request: Send a blank email to internals+get-124864@lists.php.net to get a copy of this message
On Sun, Aug 11, 2024, 8:32 PM Gina P. Banyard <internals@gpb.moe> wrote: > On Sunday, 11 August 2024 at 15:26, Pierre Joye <pierre.php@gmail.com> > wrote: > > > > On Sun, Aug 11, 2024, 6:53 PM Gina P. Banyard <internals@gpb.moe> wrote: > >> On Saturday, 10 August 2024 at 15:13, Christoph M. Becker < >> cmbecker69@gmx.de> wrote: >> >> I think moving the PDO driver to use C++ is a more sensible choice. >> > > > what would be the advantages? given the OO part at the C level is > perfectly fine in C and the actual OO parts are really zend classes and co? > > > I didn't say to rewrite the whole extension. > Considering the library we are going to be depending on is in C++ it makes > more sense to do what the ext/intl extension does, which is to use C++. > I do not want the project to have to deal with a broken C transpilation > error created by an external tool (namely CLOOP). > > If you have a better suggestion on how to deal with this issue, feel free > to do so. > ah you mean only for fb? makes sense yes. While I prefer to add a thin layer to expose it as c and keep the engine&co use in c, a tat bit easier with little impact :)

« previous php.internals (#124864) next »