Re: PDO_Firebird: use C++?

On 11.08.2024 at 19:05, Pierre Joye wrote: > On Sun, Aug 11, 2024, 8:32 PM Gina P. Banyard <internals@gpb.moe> wrote: > >> 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 :) That's exactly what <https://github.com/php/php-src/pull/15230> does; there is a single C++ file pdo_firebird_utils.cpp and a small header pdo_firebird_utils.h which exposes the C API. Christoph