On 29/03/2019 12:05, Joe Watkins wrote:
No, it's broken in both modes.
In NTS mode, both the thread that handles events (which illegally calls
user code) and the main thread are executing concurrently, they may both
be calling functions that cause interaction with module globals, which
are ob
No, it's broken in both modes.
In NTS mode, both the thread that handles events (which illegally calls
user code) and the main thread are executing concurrently, they may both be
calling functions that cause interaction with module globals, which are
obviously shared between threads in NTS mode.
On Fri, Mar 29, 2019 at 10:59 AM Joe Watkins wrote:
> 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
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
On 29.03.2019 at 10:29, Benjamin Eberlei wrote:
> On Fri, Mar 29, 2019 at 10:20 AM Lester Caine 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 o
On Fri, Mar 29, 2019 at 10:20 AM Lester Caine wrote:
> On 29/03/2019 08:50, Benjamin Eberlei wrote:
> > So it looks like I'm going to be stuck on PHP7.3 from now on ...
> >
> >
> > I think you misunderstand what is happening here.
> >
> > Many extensions are "just" in PECL and are still maint
On 29/03/2019 08:50, Benjamin Eberlei wrote:
So it looks like I'm going to be stuck on PHP7.3 from now on ...
I think you misunderstand what is happening here.
Many extensions are "just" in PECL and are still maintained there and
kept updated for newer versions. Distribution maintainers l
On Fri, Mar 29, 2019 at 9:41 AM Lester Caine wrote:
> On 29/03/2019 06:05, Stanislav Malyshev wrote:
> >> News to me is
> >> https://firebirdsql.org/en/news/revival-of-php-driver-development/, but
> >> then many Firebird user groups do not have English as a first language
> >> and just get on wit
On 29/03/2019 06:05, Stanislav Malyshev wrote:
News to me is
https://firebirdsql.org/en/news/revival-of-php-driver-development/, but
then many Firebird user groups do not have English as a first language
and just get on with things locally.
Well, this sounds good, but are these people going to d
Hi!
> News to me is
> https://firebirdsql.org/en/news/revival-of-php-driver-development/, but
> then many Firebird user groups do not have English as a first language
> and just get on with things locally.
Well, this sounds good, but are these people going to develop it outside
PHP project? Or ar
On 25/03/2019 22:54, Stanislav Malyshev wrote:
That means both extensions are effectively unmaintained for over a
decade. If this does not happen, then continuing to ship it as part of
PHP core distribution is not doing the users any favors.
When critical problems have arisen they have been add
Hi Stas
Den tir. 26. mar. 2019 kl. 00.54 skrev Stanislav Malyshev :
> That means both extensions are effectively unmaintained for over a
> decade. If this does not happen, then continuing to ship it as part of
> PHP core distribution is not doing the users any favors.
Please see this RFC I recent
Hi!
> "we" are. Like are you kidding me, honestly. Can't you just say
> whether it is "we" as in:
>
> - The Firebird community
> - The Interbase community
> - or a combination?
> - Borland?
> - Aston Tate?
> - The dBase developers?
Also, I wonder could someone from the "we" come forward and sign
Den lør. 23. mar. 2019 kl. 15.59 skrev Lester Caine :
> It's lunch time here and I've just had a phone call from a client
> complaining that their site is down ... just a white screen ...
> Actually it was only a small area inside the site and I'd not picked it
> up in the several hundred pages tha
On 23/03/2019 13:30, Kalle Sommer Nielsen wrote:
This kind of behavior does not belong here in any possible way, and it
does not win you any points in favor. Take the rest of the evening off
the computer if you cannot handle the reality and issues that is present
here in the ext/interbase deb
lør. 23. mar. 2019 kl. 15.22 skrev Lester Caine :
> On 23/03/2019 12:46, Kalle Sommer Nielsen wrote:
> >> Now to get back to working out why Nikita's patch does not work in
> >> 7.2.16 ...
> > Obviously because the patch was made for PHP 7.3. Hint: If a
> > macro/function is not available in 7.2,
On Sat, Mar 23, 2019 at 2:22 PM Lester Caine wrote:
> On 23/03/2019 12:46, Kalle Sommer Nielsen wrote:
> >> Now to get back to working out why Nikita's patch does not work in
> >> 7.2.16 ...
> > Obviously because the patch was made for PHP 7.3. Hint: If a
> > macro/function is not available in 7.
Lester
lør. 23. mar. 2019 kl. 15.16 skrev Lester Caine :
> On 23/03/2019 12:47, Joe Watkins wrote:
> > The thing is broken
>
> The BLOODY THING IS WORKING PERFECTLY ... what is broken is something
> that simply currently necessitates using the resource that has already
> been created rather than
On 23/03/2019 12:46, Kalle Sommer Nielsen wrote:
Now to get back to working out why Nikita's patch does not work in
7.2.16 ...
Obviously because the patch was made for PHP 7.3. Hint: If a
macro/function is not available in 7.2, then look at how it is
implemented in 7.3 and migrate it or see how
No it is not, if it were, it would not need patching, it would not be doing
illegal things in ZTS mode and I wouldn't be getting shouted at by someone
not qualified to say if it works or not.
Consider me out of this conversation.
On Sat, 23 Mar 2019, 14:16 Lester Caine, wrote:
> On 23/03/2019 1
On 23/03/2019 12:47, Joe Watkins wrote:
The thing is broken
The BLOODY THING IS WORKING PERFECTLY ... what is broken is something
that simply currently necessitates using the resource that has already
been created rather than trying to connect again. The correct response
to someone complaini
You say lots of people are relying on it, but it is only you who speaks in
support of it. The thing is broken, it does bad things, there is no
maintainer, and not a huge userbase.
It's not the case that we are just kicking it out for convenience, it is
the case that we cannot keep it in phpsrc wit
Hi
Den lør. 23. mar. 2019 kl. 14.36 skrev Lester Caine :
> We as in the people who rally around when we need to to protect the
> things we think are important. There are more people today reliant on
> elements like Firebird than there were 20+ years ago and to be honest if
> you kick the interbase
On 23/03/2019 12:05, Kalle Sommer Nielsen wrote:
80% of this posting is more a personal blog of how you (not "we") have
been interacting with the PHP community (as in the PHP.net community
specifically). What you should have done was to reply to either me or
Dan in the RFC thread with a one liner
Hi
Den lør. 23. mar. 2019 kl. 11.28 skrev Lester Caine :
>
> Over twenty years ago Borland took over Ashton Tate to bring dBase into
> the Borland tool set. What they did not appreciate at the time was that
> Ashton Tate had taken over Interbase to provide a proper multi-user
> database engine to
25 matches
Mail list logo
