On Thu, Dec 6, 2018 at 11:29 AM Sara Golemon wrote:
> On Thu, Dec 6, 2018 at 12:14 PM Nikita Popov wrote:
>
>> Given that the PHP 7.3 release announcement is somewhat more significant
>> than our usual maintenance releases, maybe that one could be done
>> separately?
>>
>> Given that the migrati
On Thu, Dec 6, 2018 at 11:08 AM Sara Golemon wrote:
> On Thu, Dec 6, 2018 at 11:09 AM Trevor Suarez wrote:
>
>> In any case, I feel like its usually the last place where I see
>> announcements made.
>
> I'll take exception to that. I've been pushing both branc
uture, tweeting from that account can be made a part of
coordinating an announcement? Just a thought. :)
- Trevor Suarez
https://trevorsuarez.com/
On Wed, Jun 15, 2016 at 11:34 AM, Michael Felt wrote:
>
>
> On 15-Jun-16 15:55, Rowan Collins wrote:
>
>> On 15/06/2016 14:01, Peter LeBrun wrote:
>>
>>> The weirdest part about this is that PHP is somehow trying to allocate
>>> 140TB of memory.
>>>
>>
>> I've seen numbers like that a few times -
I just wanted to personally thank Sara Golemon, and the PHP internals team,
for being so incredibly approachable, open, and all-around awesome.
The fact that a simple, informal tweet can turn into a core feature is
incredible: https://twitter.com/trevorsuarez/status/709864419753377792
Thanks agai
Ah, I didn't realize this thread existed. I had just commented on the old
one, but the point still stands:
PHP 7.0 RC1 was just tagged.
Shouldn't this be a relatively high priority to fix/decide so we don't end
up with behavior that can't be fixed until PHP 8.0?
On Mon, Aug 10, 2015 at 6:54 PM Ni
PHP 7.0 RC1 was just tagged.
Shouldn't this be a relatively high priority to fix/decide so we don't end
up with behavior that can't be fixed until PHP 8.0?
On Sat, Aug 1, 2015 at 6:16 PM Scott Arciszewski
wrote:
> On Sat, Aug 1, 2015 at 6:37 AM, Nikita Popov wrote:
> > tl;dr: This should defini
On Fri, Jul 3, 2015 at 12:24 PM Nikita Popov wrote:
> Hi internals!
>
> In a previous thread on the topic [1] I promised to create an RFC for the
> soft-reservation of 'void', similar to a bunch of other reservations we
> have done for PHP 7. The RFC also includes 'enum' as an additional
> indepe
Damn Gmail... I just top-posted. I'm going to go away for a while now...
On Wed, Apr 1, 2015 at 4:19 PM Trevor Suarez wrote:
> Author of PR https://github.com/php/php-src/pull/1145 here.
>
> I'm really quite sorry. I didn't mean to create a mess here. I was jus
Author of PR https://github.com/php/php-src/pull/1145 here.
I'm really quite sorry. I didn't mean to create a mess here. I was just
trying to contribute. :/
Unfortunately, whether or not an RFC was necessary for an addition like
this wasn't very clear. I'm an internals noob, so I simply tried to
On Mon, Mar 16, 2015 at 5:04 PM Anthony Ferrara wrote:
> All,
>
> Voting has been closed on the scalar type declarations v0.5 RFC:
>
> https://wiki.php.net/rfc/scalar_type_hints_v5
>
> At a final score of 108:48, it has been accepted for PHP 7.
>
> Thank you.
>
> Anthony
>
> --
> PHP Internals -
Good morning internals!
I would like to propose a small addition be made to the DateTime class.
https://github.com/php/php-src/pull/1145
This is my first contribution to PHP's core, beyond documentation edits.
I'm not sure on the formalities that need to be taken for something like
this to be co
... well that's a constructive way of going about it. I don't think Yasuo
did anything harmful or rude in making his proposal. Regardless of how
realistic the idea may be, I don't think its ever appropriate or
constructive to tell someone to simply "stop" because something "is just
ridiculous".
On
Thank you so much for taking the time to do this. Your explanations of a
more "real-world" example are extremely valuable and provide a very strong
hint at the effects that these RFC implementations may have, both in the
short and long term.
Seriously, very appreciated.
On Thu, Feb 26, 2015 at 7:
Hi internals,
I was just browsing the RFC wiki page when I noticed a sub-section for PHP
5.7 under the Implemented section[1]. Considering that the PHP 5.7 version
RFC was put to a vote and failed[2], I'm wondering why these items are
still in this section.
Should we move these 5.7 items to the 7
I think that structure makes sense Dmitry.
Though, just a bit on naming here (I know, its not a big deal, and naming
is hard, haha):
I think that naming the new parent exception something like "Throwable" or
"Catchable" (as Nikita previously suggested) would be a bit more concise in
meaning than
Good early morning (late night for me) internals!
I would like to propose a small addition be made to the DateTime date
format constant definitions.
https://github.com/php/php-src/pull/882
This is my first contribution to PHP's core. I wasn't sure if something of
this nature would require an RFC
Great job on this Adam. You whipped this up pretty quickly and it looks
good!
On Mon Oct 27 2014 at 5:21:30 PM Adam Harvey wrote:
> On 27 October 2014 18:29, Sebastian Bergmann wrote:
> > On 10/27/2014 10:45 AM, Peter Cowburn wrote:
> >> The closest we have, at the moment, is probably http://ph
>
> If we're talking the plunge of putting exceptions into the core engine,
> wouldn't it make sense to convert most of the fatal errors (especially
> the "catchable" ones) to exceptions too? Most of them (except for out of
> memory, timeouts and such) don't really require the engine to shut down,
breaks that could help or hurt the
project and the future of the language.
*Trevor Suarez*
+Trevor Suarez <https://plus.google.com/+TrevorSuarez>
@trevorsuarez <https://twitter.com/trevorsuarez>
On Thu, Aug 21, 2014 at 2:17 PM, Stas Malyshev
wrote:
> Hi!
>
> >> And sin
20 matches
Mail list logo
