Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:104997
MIME-Version: 1.0
References: <2f7acce4-69dd-d98b-6f86-1110e3589c4b@lsces.co.uk>
 <CAJW__o0NExOzXF0MCv5o3ZnKodkNydr7OTC1+te8f-pySOsw3g@mail.gmail.com>
 <f24812d0-82eb-88f4-03e8-fefe99ab30da@gmail.com> <27d7e310-f50d-5dad-1af8-345f77dfd102@lsces.co.uk>
 <ebab7276-41f9-56d2-71bc-ce957553a917@gmail.com> <e9122d95-1f40-f856-1a23-61a666576a04@lsces.co.uk>
 <CAEPJdu=8LcHyw-fByDsDSB7mAWuvDhmhOQpN6z0BR=xYJJUDtg@mail.gmail.com>
 <f43537e2-ec63-1ef5-e7d3-478150a67eba@lsces.co.uk> <CAEPJdu=rR9VbUu6QiuOg+Qp89=UZeWRcpHWkVfQeHKnMtF037g@mail.gmail.com>
 <0c833502-1017-5432-f3d4-ac608d864a19@gmx.de>
In-Reply-To: <0c833502-1017-5432-f3d4-ac608d864a19@gmx.de>
Date: Fri, 29 Mar 2019 10:58:50 +0100
Message-ID: <CAOwTYAv3sdi7TCN3JL5zLEJC8KnYUiBy1JbfEEyStpT45+5mJg@mail.gmail.com>
To: "Christoph M. Becker" <cmbecker69@gmx.de>
Cc: Benjamin Eberlei <kontakt@beberlei.de>, Lester Caine <lester@lsces.co.uk>, 
	PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000005b9ca2058538b8cf"
Subject: Re: [PHP-DEV] Firebird - Who are WE ...
From: krakjoe@gmail.com (Joe Watkins)

--0000000000005b9ca2058538b8cf
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Specifically the events interface is broken all versions of PHP 7:

  - In a non-zts build, it executes user code allocated in Thread A in
Thread B - that's not allowed.
  - In a zts build, it makes the same mistake as above, and uses a TSRM API
to set context which itself has been broken since PHP 7.0.

It so happens that PHP 8 has broken the build, but specifically that part
of the extension has been broken since PHP 7.0.

Cheers
Joe



On Fri, 29 Mar 2019 at 10:40, Christoph M. Becker <cmbecker69@gmx.de> wrote=
:

> On 29.03.2019 at 10:29, Benjamin Eberlei wrote:
>
> > On Fri, Mar 29, 2019 at 10:20 AM Lester Caine <lester@lsces.co.uk>
> wrote:
> >
> >> Currently building 'interbase' extension has been turned off because
> >> it's failing to pass the changes in master for thread safe operation. =
I
> >> understand that it needs someone to work on it and I would love to be
> >> able to do that but it's development requirements have moved outside t=
he
> >> area that I can cope with. And many people reliant on it are in the sa=
me
> >> boat, just as they would not be able to contribute to writing code for
> >> Firebird itself. While not perfect, what we have currently does it's j=
ob
> >> just as PHP5.2 still works on legacy hosting. PDO hopefully will remai=
n
> >> available, but re-writing 20 years worth of code base for that differe=
nt
> >> way of working has the same problem as finding resources to update the
> >> interbase extension.
> >
> > PHP needs to support thread safety in all its extensions, but that
> doesn't
> > mean its required for PECL extensions. You probably run PHP in NTS mode=
,
> > and if the interbase extension supports that, no need to add thread
> safety
> > support while in PECL. The problem is that every extension in php-src
> MUST
> > support it, because php supports it.
> >
> > To me it feels you are blowing this issue way out of proportion. Please
> > believe everyone trying to tell you over and over again that you have
> > nothing to fear from this unbundling.
>
> ext/interbase is indeed broken (i.e. uncompilable) in master (not PHP
> 7.4 though), since PR #3976[1] has been merged.  It will certainly be
> fixed, if the =E2=80=9CUnbundle ext/interbase=E2=80=9D RFC[2] will be dec=
lined; if it
> will be accepted it might never get fixed.
>
> [1] <https://github.com/php/php-src/pull/3976>
> [2] <https://wiki.php.net/rfc/deprecate-and-remove-ext-interbase>
>
> --
> Christoph M. Becker
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--0000000000005b9ca2058538b8cf--