Evening,
The PHP team announces the release of PHP 7.1.17, a security release. All
users of PHP 7.1 are encouraged to upgrade.
Changes can be found: http://php.net/ChangeLog-7.php#7.1.17
Downloads are available: https://secure.php.net/downloads.php#v7.1.17
Verification information follows:
Evening all,
PHP 7.1.15RC1 is available for testing, downloads are at:
https://downloads.php.net/~ab
Please note, downloads are not in the normal location, and php-web may not
have updated just yet: I have a very poor internet connection and had to
call on the help of comrades to get this done.
+1
It's true that everyone can setup their own filters, but why should they
have too.
You don't get to conduct yourself however you want without consequence.
Cheers
Joe
On Wed, Jan 3, 2018 at 6:52 PM, Rowan Collins
wrote:
> On 3 January 2018 at 17:28, Chase Peeler
Cheers
Joe
On Wed, Jan 3, 2018 at 7:45 PM, Paul Jones <pmjone...@gmail.com> wrote:
>
> > On Jan 3, 2018, at 12:35, Joe Watkins <pthre...@pthreads.org> wrote:
> >
> > You don't get to conduct yourself however you want without consequence.
>
> Sure. The question
Afternoon all,
PHP 7.1.21RC1 is available for testing and can be downloaded from
https://downloads.php.net/~ab
Windows binaries can be found at http://windows.php.net/qa/
Follows is verification information:
php-7.1.21RC1.tar.bz2
SHA256 hash:
Afternoon internals,
I'd like to bring https://wiki.php.net/rfc/abolish-narrow-margins to vote
in the very near future ...
We discussed it a year ago, and discussion died down to nothing (possibly
because it was sidetracked); If there are no objections I'll bring it to
vote in the coming days
Zeev,
> I think our voting rules are in need of a much thorough review than just
pushing the limit to 2/3 - which also IMHO doesn't tackle the difference
scenarios that exist out there.
Agree, they need reform, but rather than trying to discuss and pass a
monolithic RFC that tries to solve all
Afternoon everyone,
PHP 7.1.16RC1 is available for testing at https://downloads.php.net/~ab
Please report any bugs you find.
Follows is verification information:
php-7.1.16RC1.tar.bz2
SHA256 hash:
f95247efac6caacf74e78a23f7ec14416cbfb66711f839af04b022559e1b1632
PGP signature:
-BEGIN PGP
Evening Sara,
You forgot to mention the free cake you get for being an RM ...
Cheers
Joe
On Tue, Apr 24, 2018 at 9:03 PM, Stanislav Malyshev
wrote:
> Hi!
>
> > I want to encourage anyone who is "on the fence" or worried they won't
> > be able to pull it off to just go for
Afternoon,
PHP 7.1.15 has been released and is available for download at
https://downloads.php.net
Windows binaries are available on http://windows.php.net
Follows is verification information:
php-7.1.15.tar.bz2
SHA256 hash:
e117a54738e9485de5fc75673d39dbe937dd87f0f9cc9e281960ef9b961adcbd
PGP
2.2250738585072E-308
This is negative.
Cheers
Joe
On Wed, 3 Apr 2019 at 12:27, Diogo Neves wrote:
> It really don't make much sense:
>
>
> var_dump( PHP_FLOAT_MIN < 0 );
> var_dump( PHP_INT_MIN < 0 );
>
> On Wed, Apr 3, 2019 at 10:52 AM Benjamin Morel
> wrote:
>
> > Hi internals,
> >
> > I
Such complex and far reaching features should clearly have a two week
voting period, please update the RFC.
Cheers
Joe
On Thu, 21 Mar 2019 at 12:58, Dmitry Stogov wrote:
> Hey,
>
> I'm starting the vote on JIT RFC.
>
>
>
019 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 s
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
Thanks for explain.
Cheers
Joe
On Wed, 3 Apr 2019 at 14:40, Rowan Collins wrote:
> On Wed, 3 Apr 2019 at 13:33, Benjamin Morel
> wrote:
>
> > PHP_FLOAT_MIN (float)
> > > Smallest representable POSITIVE floating point number. If you need the
> > > smallest representable floating point number,
The PHP development team announces the immediate availability of PHP
7.1.28. This is a security release.
All PHP 7.1 users are encouraged to upgrade to this version.
For source downloads of PHP 7.1.28 please visit our downloads page.
Windows binaries can be found on the PHP for Windows site.
The
Afternoon internals,
Abolish Short Votes is now in voting:
https://wiki.php.net/rfc/abolish-short-votes
Cheers
Joe
T, it's probably going to be changed a lot in the nearest
> future.
>
>
> Thanks. Dmitry.
> --
> *From:* Joe Watkins
> *Sent:* Friday, March 29, 2019 3:40:04 PM
> *To:* release-manag...@php.net; PHP internals; Dmitry Stogov
> *Subject:* PHP
Morning internals,
Since we now have a result for JIT and we know it will be included in PHP
8, I think it's time to visit the idea brought up in discussion to have
preview releases of PHP 8.
I'm interested in hearing what kind of schedules we think are going to be
useful - it's tempting to say
Morning Levi,
For me, as author of many extensions, pickle becomes valuable at the point
when composer supports it and we have another route to deployment built
into composer.
Currently, there is no remarkable difference between using pecl or pickle
to build, except pecl is available everywhere,
Morning Dmitry,
Thanks for all your hard work on this, thanks also to Anatol for making
Windows and ZTS happen.
Thank you in advance for all the work to come :)
PHP 8 is going to be quite special, I think, I look forward to it ..
Cheers
Joe
On Fri, 29 Mar 2019 at 09:58, Dmitry Stogov 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 TSRM API
to set context which itself has been broken since
:
>
>
> 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
he vote ?
Are we going to invent a set of criteria that would invalidate the vote ?
This seems like a rabbit hole we need not get stuck in.
Cheers
Joe
On Fri, 22 Mar 2019 at 17:01, Chase Peeler wrote:
>
> On Fri, Mar 22, 2019 at 3:41 AM Joe Watkins wrote:
>
>> Morning Niklas,
>>
Sara, where do I send pull requests?
wrote:
> I've always wondered why PHP didn't have a built in command or function
> that behaved as `echo` but with a EOL.
> I propose not to modify `print` or `echo` (as this was rightly pointed out
> to cause b/c). How difficult would it be to add a new
Afternoon Steven,
I'm not going to apologize for making a joke ... it was a joke ...
That being said, if you insist on pursuing an RFC for this, and would like
to get on with writing that RFC, then here is an initial patch:
https://gist.github.com/krakjoe/efff492611ce8f9fc12909023c89c7dc
Let
Hi all,
It would be nice to hear from Peter , do you want to take on this role ?
You would have my vote, obviously, but we like people to volunteer, it's
not a small or short commitment.
Cheers
Joe
On Wed, 6 Mar 2019 at 10:39, Kalle Sommer Nielsen wrote:
> Den ons. 6. mar. 2019 kl. 11.03
Thanks for all the effort Dmitry, it's looking in much better shape.
Cheers
Joe
On Fri, 22 Feb 2019 at 13:18, Dmitry Stogov wrote:
> Hi Internals,
>
>
> The RFC and implementation was updated once again.
>
>
> https://wiki.php.net/rfc/jit
>
>
> Now JIT supports PHP builds with compilers
Morning all,
The abolish narrow margins RFC has been accepted and the Voting RFC has
been updated and had it's version changed to 1.1
Cheers
Joe
Morning all,
The vote for weakrefs is open: https://wiki.php.net/rfc/weakrefs
Cheers
Joe
Whoever creates the pecl package would be listed as maintainer, which may
explain silence :)
I'm not sure who has karma for creating repos on git.php.net either, I may ?
Cheers
Joe
On Mon, 25 Feb 2019, 12:10 Christoph M. Becker, wrote:
> On 11.02.2019 at 19:42, Christoph M. Becker wrote:
>
>
As a function it has parity with fputs ... even though fputs doesn't have
the same behaviour the two can be considered complimentary, and you would
want to be able to cuf(a) puts like fputs.
Regardless an RFC may go ahead without optimized implementation.
Cheers
Joe
On Sun, 10 Mar 2019, 20:28
Afternoon,
The PHP development team announces the immediate availability of PHP
7.1.27. This is a security release.
All PHP 7.1 users are encouraged to upgrade to this version.
For source downloads of PHP 7.1.27 please visit our downloads page.
Windows binaries can be found on the PHP for
Apologies,
I missed the verification info for 7.1.27:
php-7.1.27.tar.bz2
SHA256 hash:
dad7ecd30941911528e471c555a01911a68aa9219696bfc1e005f8b669f4ec4b
PGP signature:
-BEGIN PGP SIGNATURE-
iQEcBAABCAAGBQJcfs5MAAoJEPm6Ctoxy9iedkYH/2IyMTgmUGfPQdK96nXGZX8T
on, wrote:
> Den 2019-03-19 kl. 17:53, skrev Sebastian Bergmann:
> > Am 19.03.2019 um 17:43 schrieb Joe Watkins:
> >> At least I'd like someone to explain in detail why we should extend
> >> support
> >> for 7.4?
> >
> > Seconded.
> >
> For u
https://pecl.php.net/package/wddx
Cheers
Joe
On Wed, 20 Mar 2019 at 13:03, Christoph M. Becker wrote:
> On 13.03.2019 at 20:47, Christoph M. Becker wrote:
>
> > Still, I'm looking for someone who is willing to create a new home for
> > ext/wwdx on PECL.
>
> This is just a gentle reminder that
Looks like someone done that too, I think you have everything you need now ?
Cheers
Joe
On Wed, 20 Mar 2019 at 13:29, Christoph M. Becker wrote:
> On 20.03.2019 at 13:09, Joe Watkins wrote:
>
> > https://pecl.php.net/package/wddx
>
> Thanks Joe! My request was badly worded,
Maybe put a readme in the git repo ...
Cheers
Joe
On Wed, 20 Mar 2019 at 14:04, Nikita Popov wrote:
> On Wed, Mar 20, 2019 at 1:43 PM Joe Watkins wrote:
>
>> Looks like someone done that too, I think you have everything you need
>> now ?
>>
>> Cheers
>> Jo
I'm not so sure it's worth adopting as policy. It's.my understanding that
5.6 was extended for reasons that may not apply to the 7.4-8 upgrade. It's
likely less painful, it's likely better prepared with 7.4 raising
appropriate deprecation notices and such.
At least I'd like someone to explain in
Cheery picked into 7.1
Cheers
Joe
On Mon, 11 Mar 2019 at 17:35, Christoph M. Becker wrote:
> On 19.02.2019 at 02:16, Stanislav Malyshev wrote:
>
> >> In my opinion, adding this ini setting to PHP-7.4 is a no brainer, but I
> >> suggest that we backport it to PHP-7.2 as well.
> >
> > I don't
Morning internals,
The vote for weakrefs is closed and has been accepted.
Because of feedback received very late during voting from non-voting
contributors/community members, the implementation will be slightly
different to that in the RFC - it was pointed out that it's more useful if
there is
ting
> period.
>
> If you liked to change this, you might do it together with 50%+1 -> 2/3
> majority change.
>
>
> If you agree, I can extend voting period "pseudo proportionally" (to be
> 1.5 week), but I don't like to lose the following week.
>
>
&
Evening internals,
I'd like to raise for discussion another minor, self contained change to
the voting RFC:
https://wiki.php.net/rfc/abolish-short-votes
This seems like another no-brainer to improve and clarify the voting
process. As with abolishing narrow margins, I'm focused on this one
Morning Kalle,
Seems like a reasonable plan, +1
Cheers
Joe
On Fri, 22 Mar 2019 at 14:26, Kalle Sommer Nielsen wrote:
> G'day internals
>
> I'd like to start the discussion for the future of the ext/interbase
> extension:
> https://wiki.php.net/rfc/deprecate-and-remove-ext-interbase
>
> The
ys in
> case the author didn't think about that when starting the vote.
>
> Regards, Niklas
>
> Joe Watkins schrieb am Do., 21. März 2019, 19:20:
>
> > Evening internals,
> >
> > I'd like to raise for discussion another minor, self contained change to
> > th
Hi Adrian,
Thanks for your interest in contributing to PHP, the necessary karma has
been granted to you.
I will just mention that I believe there's more than one person working on
annotation proposals as well as declined proposals, it would be a good idea
to liaise with current and past authors
Hi Paul,
Thanks for you interest in contributing to PHP, the necessary karma has
been granted to you.
Cheers
Joe
On Wed, 6 Feb 2019 at 11:26, Paul Crovella wrote:
> I'd like to do some work on a Partial Function Application RFC. Could
> someone grant the wiki user pcrov the necessary karma?
>
Morning all,
As promised, abolish narrow margins is now open for voting:
https://wiki.php.net/rfc/abolish-narrow-margins
Cheers
Joe
Dmitry Stogov wrote:
>
>>
>>
>> On 2/6/19 11:50 AM, Nikita Popov wrote:
>> > On Thu, Jan 31, 2019 at 1:59 PM Joe Watkins wrote:
>> >
>> >> Afternoon internals,
>> >>
>> >> Some time ago I brought up for discussion:
>
onfidence
has evaporated, I'm sorry to say.
Cheers
Joe
On Fri, 15 Feb 2019 at 09:06, Dmitry Stogov wrote:
> Hi,
>
> On 2/14/19 5:22 PM, Joe Watkins wrote:
> > Morning all,
> >
> > This idea of an experimental feature as complex as a JIT is dangerous. It
> >
Morning all,
I'm very pleased to see effort going into this, and the resulting ideas.
I don't have anything to add about the implementation.
Since most people are not interested in ZTS, there aren't going to be many
voices pushing you to actually make changes, so I want to be that voice.
The
What you describe is first class support for classes, nothing much to do
with anonymous classes.
On Wed, 13 Feb 2019, 09:01 Rasmus Schultz The fact that the anonymous class syntax defines a class *and* immediately
> constructs an instance is quite annoying.
>
> For one, this is quite
Morning all,
This idea of an experimental feature as complex as a JIT is dangerous. It
is not finished, and dmitry has said he's not willing to put more time into
until it's merged. That's his prerogative, and it is ours to say that we
don't want unfinished software that only one or two people
ote:
>
> > On 14.02.2019 at 12:56, Zeev Suraski wrote:
> >
> > > On Wed, Feb 13, 2019 at 11:26 AM Joe Watkins
> wrote:
> > >
> > >> The ZTS build is very commonly used in Windows today
> > >
> > > Any idea why?
> >
> > windows.ph
Packages such as xampp, which are very widely used, bundle a thread safe
interpreter.
It's a fact that ZTS is important on Windows.
Cheers
Joe
On Thu, 14 Feb 2019 at 16:22, Rowan Collins wrote:
> On Thu, 14 Feb 2019 at 11:57, Zeev Suraski wrote:
>
> > On Wed, Feb 13, 2019 at
nformal.
>
> Thanks. Dmitry.
>
>
>
>
> > Cheers
> > Joe
> >
> > On Wed, 6 Feb 2019 at 17:31, Nikita Popov > <mailto:nikita@gmail.com>> wrote:
> >
> > On Wed, Feb 6, 2019 at 4:38 PM Dmitry Sto
Morning Dmitry, and internals,
This is marvellous stuff, truly brilliant. I particularly appreciate the
non-intrusive approach of setting jit'd code as the opcode handler, this
makes life a little easier for hacky extension authors, I think.
As others have said:
I don't like the idea of
Morning Stas, and all,
This discussion was ... a mess, partly my fault, I suppose.
I said I was going to bring it up for voting quickly on the say so of
Nikita, and because it feels urgent to us, you can guess our reasons for
that.
I'm not going to argue back and forth for the next week about
+1
On Fri, 1 Feb 2019 at 12:35, Sebastian Bergmann wrote:
> Am 01.02.2019 um 12:27 schrieb Nikita Popov:
> > I would like to suggest that installation of PEAR is disabled by default
> in
> > PHP 7.4. PR: https://github.com/php/php-src/pull/3781
>
> +1
>
> --
> PHP Internals - PHP Runtime
Morning internals,
Some time ago I brought this up for discussion, and last night was reminded
of it's existence, and so this morning rebased and reworked the patch a
little based on the feedback I got back then.
Since it was long ago, and there's no particular rush, I don't intend to
open
Afternoon Christoph,
I can't really think of another name ... it's ... a weakref ...
Probably using the PHP namespace makes most sense.
Cheers
Joe
On Sun, 3 Feb 2019 at 18:40, Christoph M. Becker wrote:
> On 02.02.2019 at 09:35, Joe Watkins wrote:
>
> > Some time ago I bro
Updated patch, name is WeakReference.
Cheers
Joe
On Sun, 3 Feb 2019 at 19:39, Joe Watkins wrote:
> Does that solve the problem for you Christoph ?
>
> Cheers
> Joe
>
> On Sun, 3 Feb 2019 at 19:08, Robert Korulczyk wrote:
>
>>
>> > I can't really think of
quite a lot of junk on there ...
Cheers
Joe
On Sun, 3 Feb 2019 at 19:56, Christoph M. Becker wrote:
> On 03.02.2019 at 19:39, Joe Watkins wrote:
>
> > Does that solve the problem for you Christoph ?
>
> Yes, calling the class WeakReference would be fine for me.
>
> --
> Christoph M. Becker
>
Does that solve the problem for you Christoph ?
Cheers
Joe
On Sun, 3 Feb 2019 at 19:08, Robert Korulczyk wrote:
>
> > I can't really think of another name ... it's ... a weakref ...
>
> It is actually "weak reference", so why not WeakReference?
>
>
> Regards,
> Robert Korulczyk
>
Just a quick note ...
I should say that bug fixes should not require an RFC at all, but the line
between bug, quick fix and feature is blurry. Sometimes it is necessary to
gather consensus and voting is the most effective way we have to do that.
Cheers
Joe
On Sat, 2 Feb 2019 at 18:13, Joe
Hi Nikita,
I can't be helpful here at all, because (shamefully) allergic to and bad at
windows, and no experience at all with azure.
But I would really like our CI to be restored to a thing that's useful,
instead of running two jobs on travis, and more or less nothing on av (most
of the time).
Afternoon Nikita, internals,
In stark contrast to the proposals being made to make contributing to PHP
more complex, slower, and burdened with bureaucracy: These are elegant
proposals that I think will invite new contributors to join our ranks,
which we no doubt need. They will allow current
Hi Legale,
In general we leave the packaging of PHP to the packaging experts. So I
doubt if there's much need to include these in php-src, but let's see what
others have to say ?
Cheers
Joe
On Sat, 2 Feb 2019 at 20:24, Legale Legage wrote:
> Hello, internal.
>
> I want to propose including to
Hi Legale, internals,
> I want to say that even a small and fairly
simple code change,
which I proposed to push through the bureaucracy, was difficult.
This, I am afraid is all too common. Many many times, while working through
github issues, I will be uncomfortable with making a merge for
Afternoon internals,
Some time ago I brought up for discussion:
https://wiki.php.net/rfc/abolish-narrow-margins
I intend to bring this up for vote in the next few days.
Cheers
Joe
will be
taken into consideration when you cast your vote.
I do insist, and will not be waiting two weeks, unless you agree to delay
the JIT RFC until this issue is resolved.
Cheers
Joe
On Thu, 31 Jan 2019 at 14:07, Zeev Suraski wrote:
> >-Original Message-
> >From:
Afternoon internals,
Some time ago I brought up for discussion:
https://wiki.php.net/rfc/abolish-narrow-margins
I intend to bring this up for vote in the next few days.
Cheers
Joe
>
>
>
> For the record, I resent the language you used and the mal-intentions you
> attribute to me here. I’ll leave it at that.
>
>
>
> Zeev
>
>
>
> *From:* Joe Watkins
> *Sent:* Thursday, January 31, 2019 3:26 PM
> *To:* Zeev Suraski
> *Cc:* internals
king this RFC to vote.
Cheers
Joe
On Thu, 31 Jan 2019 at 16:13, Zeev Suraski wrote:
>
>
> On Thu, Jan 31, 2019 at 4:27 PM Joe Watkins wrote:
>
>> Afternoon Zeev,
>>
>> I'm going to use unambiguous and direct language to make sure my
>> inten
Hi Zeev, Dmitry,
It is not my only concern, I'm grateful for the clarification whatever.
These are your actual words from the RFC:
> This works, but this functionality is not supported on all libffi
platforms, it is not efficient and leaks resources by the end of request.
It's recommended to
Hi all,
I have considered maps ... since it is possible to do in userland, I don't
consider it super urgent, and even if you do, it doesn't become urgent
until PHP 7.4 is much closer to release.
So, we have almost a year; If this flies in, it's *highly* likely I'll
follow it up ... but don't
Hi Kalle,
You forgot to move to voting on the RFC index.
Cheers
Joe
On Tue, 9 Apr 2019, 19:07 Kalle Sommer Nielsen, wrote:
> Den tir. 9. apr. 2019 kl. 20.02 skrev Kalle Sommer Nielsen >:
> >
> > Evening Internals
> >
> > Apologies for the one day delay, but the voting for the RFC "Unbundle
>
I think this may be related to the ssl issues from earlier today, may have
been overlooked ?
Cheers
Joe
Morning all,
Nikita and I have finished setting up Azure Pipelines now: We have a 4
build configuration, which tests PHP in all permutations of Release/Debug
ZTS/NTS Opcache/NoOpcache/JIT.
Because of the way I've set it up, my name is in the url, so this morning I
went to create a PHP
Oh to be absolutely clear, I'm talking about commits that *only* touch
these non-source files ...
Cheers
Joe
On Fri, 7 Jun 2019 at 13:07, Joe Watkins wrote:
> Hi Marco,
>
> It wasn't a topic for discussion, it was a request to committers in
> php-src.
>
> We do not need
Cowburn wrote:
>
>
> On Fri, 7 Jun 2019 at 12:09, Joe Watkins wrote:
>
>> Oh to be absolutely clear, I'm talking about commits that *only* touch
>> these non-source files ...
>>
>> Cheers
>> Joe
>>
>> On Fri, 7 Jun 2019 at 13:07, Joe Watkins
> 2. You never know what can break, that's why it's "continuous" there
> (besides religious views around what "continuous integration" means)
>
> On Fri, Jun 7, 2019, 12:51 Joe Watkins wrote:
>
> > Hi all,
> >
> > Just a friendly reminder that
Hi all,
Just a friendly reminder that when we're committing changes to files that
do not contain source, test code, or build configuration, it's helpful to
include [ci skip] in the commit message. Omitting it can put our CI quite
far behind.
Cheers
Joe
Evening internals,
PHP-7.4 and master have been setup to run CI on Azure, Azure having much
more resources than Travis, we can run tests in all permutations of
Debug/Release, NTS/ZTS, with and without opcache, and with JIT.
It's possible to setup mac/windows on Azure, although myself and Nikita
Evening,
The PHP development team would like to announce the immediate availability
of PHP 7.1.30.
This is a security release and all PHP 7.1 users are encouraged to upgrade.
For source downloads of PHP 7.1.30 please visit our downloads page. Windows
binaries can be found on the PHP for Windows
Hi Christoph,
I'm not even certain this needs to be put to a vote ... we should not be
shipping that.
+1 whatever ...
If you can't find a single dissenting voice, just get rid of the thing
before the next alpha, or possibly the first beta/rc ...
Cheers
Joe
On Fri, 14 Jun 2019 at 14:27,
Just for clarity, I think the next version will be 8, right?
Cheers
Joe
On Fri, 14 Jun 2019, 16:22 Derick Rethans, wrote:
> Dear Internallers,
>
> With 7.4.0alpha1 having been released yesterday, the feature freeze for
> PHP 7.4 is coming up fast.
>
> Feature Freeze is *Monday July 22nd,
Evening all,
I've prepared an alternative: https://github.com/php/php-src/pull/4282
Hiding the arguments seems sensible enough, not as a hardcoded default
(default behaviour should be retained), but as a documented recommended
default for production.
I think, this needs to go through the RFC
The implementation of this does not look ready, there are conflicts so I
can't test it locally, but last time CI ran there were many failures.
Cheers
Joe
On Wed, 19 Jun 2019 at 09:24, Scott Dutton wrote:
> Hi all
>
> I have put my RFC base convert changes to vote this morning
>
>
easier for 2 prs ? one for each vote ?
>
> Thanks
>
> Scott
>
>
> On 19.06.2019 08:31, Joe Watkins wrote:
> > The implementation of this does not look ready, there are conflicts
> > so I can't test it locally, but last time CI ran there were many
> > failures.
&g
It will likely be easier if the Allow negative numbers implementation
(targetting master only) is entirely separate from the Error on ignored
characters implementation,.
Cheers
Joe
On Wed, 19 Jun 2019 at 09:56, Joe Watkins wrote:
> There should probably be a PR targeting
Evening,
There doesn't seem to be a patch or implementation.
Aside from the proposed semantics, which I can't really read because the
document is malformed, the most important questions for me are: How is this
going to work? Can it be done without significant complexity in the
compiler or VM?
anks. Dmitry.
> ------
> *From:* Joe Watkins
> *Sent:* Wednesday, June 12, 2019 9:38:54 PM
> *To:* Derick Rethans
> *Cc:* Dmitry Stogov; PHP Developers Mailing List
> *Subject:* Re: commit 374f76998 causes getenv to be define with Xdebug
> loaded
>
> Hi all,
>
> My
Hi all,
My clumsy ass reverted that in PHP-7.4, totally and utterly by accident,
and since it resolved Dericks problem, I went ahead and reverted in master
also rather than make maybe unnecessary noise.
Very very sorry about that, I totally intended to get Dmitry's
approval/opinion.
Terrible
Just a note on process.
It is not necessary to hold multiple RFC's:
> For procedural reasons, multiple RFCs may be combined into one, in which
case there may be multiple primary votes.
> Combining multiple RFCs into one does not allow turning a primary vote
into a secondary vote.
In general,
Hi all,
Does anyone know what is the cause of all the spam from the announce
mailing list? I'm not sure who is getting it, but I'm getting a few emails
a minute sometimes, it's rather annoying ...
Can someone do some magic, and make it go away please ?
Cheers
Joe
Morning Nikita,
It would be wise to do a) and b) regardless of whether it's going to be
removed.
I think +1 on removing it in 8 ... I'm not sure if it should be deprecated
in 7.4 first, or how that would work ?
Cheers
Joe
On Tue, 7 May 2019 at 12:11, Nikita Popov wrote:
> Hi internals,
>
>
Morning internals,
The abolish short votes RFC has been accepted and the Voting document
updated.
Cheers
Joe
Morning,
I pretty much just echo what Sara said, I'm not sure what harm they are
doing ...
Cheers
Joe
On Mon, 19 Aug 2019 at 04:09, Sara Golemon wrote:
> On Sun, Aug 18, 2019 at 6:06 PM G. P. B. wrote:
>
> > It seems this topic already has been raised a year ago [1] but nothing
> has
> >
We already have a git repository where we keep historical branches, we
don't need to create another.
I'm really not sure what the problem is here, and we have spent far too
long discussing this non issue.
Cheers
Joe
On Mon, 19 Aug 2019 at 23:23, Olumide Samson wrote:
> >
> > Maybe it might
401 - 500 of 572 matches
Mail list logo