Re: [PHP-DEV] PHP7 Coalesce operator

Hey, thanks for responding. However, I still think that misses the point, or at least the true utility of what I’m proposing. In practice, you can ignore E_NOTICE and php will happily treat null and !isset() as the same thing in *most* cases, so that’s not a good indicator of truthiness.

Re: [PHP-DEV] PHP7 Coalesce operator

Er, that should read, “anything non (null, false, undefined) is true” > On Nov 23, 2015, at 11:51 AM, shadda wrote: > > Hey, thanks for responding. > > However, I still think that misses the point, or at least the true utility of > what I’m proposing. > > In practice, you

[PHP-DEV] Benchmark Results for PHP Master 2015-11-23

Results for project PHP master, build date 2015-11-23 05:27:16+02:00 commit: 56b584491bb4644f731427452ff6401ca06a55cf revision date: 2015-11-23 03:15:46+01:00 environment:Haswell-EP cpu:Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz 2x18 cores, stepping 2, LLC 45 MB

Re: [PHP-DEV] INDRECT in arrays causes count() to become unpredictable

On Mon, Nov 23, 2015 at 12:23 PM, Phil Sturgeon wrote: > It sounds like a fix exists which people are happy with, and some > folks are ok not making another RC. Discuss that aspect. Do a little > poll on that. Done. Here is a little poll:

Re: [PHP-DEV] INDRECT in arrays causes count() to become unpredictable

Den 2015-11-23 kl. 08:28, skrev Anatol Belski: Hi, -Original Message- From: Rasmus Lerdorf [mailto:ras...@lerdorf.com] Sent: Sunday, November 22, 2015 11:20 PM To: Anthony Ferrara ; Zeev Suraski Cc: internals@lists.php.net Subject: Re: [PHP-DEV]

Re: [PHP-DEV] PHP7 Coalesce operator

> In practice, you can ignore E_NOTICE and php will happily treat null and > !isset() as the same thing in *most* cases, so that’s not a good indicator of > truthiness. If you really believe that then this is all you need already: $database = $config['database'] ?: 'db'; Correct? -- PHP

Re: [PHP-DEV] PHP7 Coalesce operator

On Mon, Nov 23, 2015 at 9:52 AM, shadda wrote: > Er, that should read, “anything non (null, false, undefined) is true” > >> On Nov 23, 2015, at 11:51 AM, shadda wrote: >> >> Hey, thanks for responding. >> >> However, I still think that misses the point, or at

Re: [PHP-DEV] PHP7 Coalesce operator

Oh, please, by no means take that as an endorsement for dropping error reporting levels. It was just an observation of how PHP actually derives a conditional in those situations. It’s not as if there’s a fatality in script execution when you make that kind of comparison, it’s just a really

Re: [PHP-DEV] PHP7 Coalesce operator

It’s not hate, I happen to like that ?? was added. I’m not raising a concern nor asking for a change in its behavior. Rather, I’m asking for another, similar operator that’s based on truth-evaluation (with PHP’s tender, loving conversion rules baked in), in *addition* to ?? which tests for

Re: [PHP-DEV] INDRECT in arrays causes count() to become unpredictable

Hey: On Mon, Nov 23, 2015 at 3:52 PM, Joe Watkins wrote: > Morning Anatol, > > > People that don't test RC won't start to test any later RC anyway. > > This wasn't reported by "people", this was found by one of us. > > The problem isn't only that we have a bug in symbol

Re: [PHP-DEV] INDRECT in arrays causes count() to become unpredictable

On 11/23/2015 09:49 AM, Phil Sturgeon wrote: > The "There will always be bugs" argument is a strawman, nobody is > saying wait until it's perfect. > > People in this thread are consistently conflating "there will always > be bugs" with "lets just ignore this bug which is 'around critical' > and

Re: [PHP-DEV] INDRECT in arrays causes count() to become unpredictable

On 23 November 2015 at 09:08, Rasmus Lerdorf wrote: > On 11/23/2015 09:49 AM, Phil Sturgeon wrote: > > The "There will always be bugs" argument is a strawman, nobody is > > saying wait until it's perfect. > > > > People in this thread are consistently conflating "there will

Re: [PHP-DEV] INDRECT in arrays causes count() to become unpredictable

> On 23 בנוב׳ 2015, at 0:35, Rafael Dohms wrote: > >> On Sun, Nov 22, 2015 at 11:19 PM, Rasmus Lerdorf wrote: >> Let's get 7.0.0 out the door and get ourselves on >> track for regular point releases without any of this "perfect-release" >> stress.

Re: [PHP-DEV] INDRECT in arrays causes count() to become unpredictable

On Mon, Nov 23, 2015 at 11:17 AM, Rasmus Lerdorf wrote: > On Nov 23, 2015, at 10:35, Derick Rethans wrote: >> >>> On November 23, 2015 10:08:18 AM GMT+01:00, Rasmus Lerdorf >>> wrote: On 11/23/2015 09:49 AM, Phil Sturgeon wrote:

Re: [PHP-DEV] INDRECT in arrays causes count() to become unpredictable

On Sun, Nov 22, 2015 at 10:12 PM, Xinchen Hui wrote: > Hey: > > On Mon, Nov 23, 2015 at 3:52 PM, Joe Watkins wrote: > >> Morning Anatol, >> >> > People that don't test RC won't start to test any later RC anyway. >> >> This wasn't reported by "people",

Re: [PHP-DEV] INDRECT in arrays causes count() to become unpredictable

I can only agree with Phil here. +1 for 1 week RCs if we're aiming at Dec 3rd anyway. Thanks, Niklas

Re: [PHP-DEV] INDRECT in arrays causes count() to become unpredictable

> genuinely feel strongly enough that this is indicative of further problems and another RC will provide us with more time to find similar issues or perhaps just give everyone a sense of confidence in the release. It's both of those things. Another week isn't going to cost us anything. We don't

Re: [PHP-DEV] INDRECT in arrays causes count() to become unpredictable

On Sun, Nov 22, 2015 at 8:01 AM, Xinchen Hui wrote: > Hey: > > On Sun, Nov 22, 2015 at 6:47 AM, Anthony Ferrara > wrote: > > > All, > > > > It appears that in our efforts to optimize PHP 7 we've introduced an > > inconsistency into array handling. This is

Re: [PHP-DEV] INDRECT in arrays causes count() to become unpredictable

> On 23 בנוב׳ 2015, at 10:08, Rasmus Lerdorf wrote: > >> On 11/23/2015 09:49 AM, Phil Sturgeon wrote: >> The "There will always be bugs" argument is a strawman, nobody is >> saying wait until it's perfect. >> >> People in this thread are consistently conflating "there will

Re: [PHP-DEV] INDRECT in arrays causes count() to become unpredictable

On November 23, 2015 10:08:18 AM GMT+01:00, Rasmus Lerdorf wrote: >On 11/23/2015 09:49 AM, Phil Sturgeon wrote: >> The "There will always be bugs" argument is a strawman, nobody is >> saying wait until it's perfect. >> >> People in this thread are consistently conflating

Re: [PHP-DEV] Re: Windows (Visual Studio) compiler stuff

On Mon, Nov 23, 2015 at 8:08 AM, Matt Wilmas wrote: > Hi Dmitry, > > - Original Message - > From: "Dmitry Stogov" > Sent: Monday, November 16, 2015 > > Hi Matt, >> >> On Mon, Nov 16, 2015 at 1:30 AM, Matt Wilmas >> wrote: >> >> Hi

Re: [PHP-DEV] Re: Pear fetch script problem on PHP 7.0

Hi, Thanks Ferenc for checking. trying to debug this, I've added "echo var_dump($argv);" in the begining of the script, but now it segfault. before: sh-3.2# /php-7.0.0RC7/sapi/cli/php -n /php-7.0.0RC7/pear/fetch.php " http://5.77.39.20/install-pear-nozlib.phar; pear/install-pear-nozlib.phar

Re: [PHP-DEV] INDRECT in arrays causes count() to become unpredictable

On Nov 23, 2015, at 10:35, Derick Rethans wrote: > >> On November 23, 2015 10:08:18 AM GMT+01:00, Rasmus Lerdorf >> wrote: >>> On 11/23/2015 09:49 AM, Phil Sturgeon wrote: >>> The "There will always be bugs" argument is a strawman, nobody is >>> saying wait

Re: [PHP-DEV] INDRECT in arrays causes count() to become unpredictable

> On 23 בנוב׳ 2015, at 14:04, Joe Watkins wrote: > > > No one is expecting 0.0 or any version to be bug free, but the simplicity of > the fix says nothing about the seriousness of the bug. I think it quite > serious _because_ we are a few days from GA, had this been

Re: [PHP-DEV] INDRECT in arrays causes count() to become unpredictable

On Nov 23, 2015, at 15:05, Zeev Suraski wrote: > >> On 23 בנוב׳ 2015, at 14:04, Joe Watkins wrote: >> >> >> No one is expecting 0.0 or any version to be bug free, but the simplicity of >> the fix says nothing about the seriousness of the bug. I think it

Re: [PHP-DEV] INDRECT in arrays causes count() to become unpredictable

Zeev and all, On Mon, Nov 23, 2015 at 9:05 AM, Zeev Suraski wrote: > > >> On 23 בנוב׳ 2015, at 14:04, Joe Watkins wrote: >> >> >> No one is expecting 0.0 or any version to be bug free, but the simplicity of >> the fix says nothing about the seriousness of

Re: [PHP-DEV] INDRECT in arrays causes count() to become unpredictable

On 23.11.2015, at 04:02, Rasmus Lerdorf wrote: > > On Nov 23, 2015, at 00:48, Adam Harvey wrote: >> >> Here's an alternative suggestion: we've previously switched to one >> week RC cycles late in the piece when trying to get major releases >> stabilised and

Re: [PHP-DEV] INDRECT in arrays causes count() to become unpredictable

Hey: On Mon, Nov 23, 2015 at 10:21 PM, Anthony Ferrara wrote: > Zeev and all, > > On Mon, Nov 23, 2015 at 9:05 AM, Zeev Suraski wrote: > > > > > >> On 23 בנוב׳ 2015, at 14:04, Joe Watkins wrote: > >> > >> > >> No one is expecting 0.0

Re: [PHP-DEV] INDRECT in arrays causes count() to become unpredictable

> On 23 בנוב׳ 2015, at 15:21, Anthony Ferrara wrote: > > Zeev and all, > >> On Mon, Nov 23, 2015 at 9:05 AM, Zeev Suraski wrote: >> >> No, but both the seriousness of the bug AND the simplicity of the fix sit >> squarely outside any sort of "critical"

Re: [PHP-DEV] 7.0.0 release

On 23/11/2015 21:10, Anatol Belski wrote: Hi, it is sad to see that the discussion went in the direction it went, but I'm glad to have missed that being away all day and at the end of it realizing my mail server messed up. Please lets get the tone down and discuss factually! I would like to

Re: [PHP-DEV] Re: Resource typehint and return type

On 23 November 2015 19:07:51 GMT, Ben Scholzen 'DASPRiD' wrote: >There's another blocker: the SplFileObject currently has no fclose() >method, which should definitely be implemented. Currently it relies on >being destroyed to close the internal resource. In case of cross

Re: [PHP-DEV] PHP7 Coalesce operator

Hi, shadda wrote: That’s not a bad idea, but it’s still limited in certain cases, where your list of possibles is, lets say, complex. At this point, I think you guys get what I’m after, and I’m wondering if anyone else finds the idea as useful I as do. In fact, if it didn’t break the One Law

Re: [PHP-DEV] 7.0.0 release

On 11/23/2015 10:10 PM, Anatol Belski wrote: c) do RC8, release on 3rd, expect there are no bugs come in +1 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DEV] 7.0.0 release

On Tue, Nov 24, 2015 at 1:00 AM, Sebastian Bergmann wrote: > On 11/23/2015 10:10 PM, Anatol Belski wrote: > >> c) do RC8, release on 3rd, expect there are no bugs come in >> > > +1 +1

Re: [PHP-DEV] 7.0.0 release

+1 C On Tue, Nov 24, 2015 at 6:18 AM, Davey Shafik wrote: > On Tue, Nov 24, 2015 at 1:00 AM, Sebastian Bergmann > wrote: > > > On 11/23/2015 10:10 PM, Anatol Belski wrote: > > > >> c) do RC8, release on 3rd, expect there are no bugs come in > >> > > > > +1 >

Re: [PHP-DEV] 7.0.0 release

> On 24 בנוב׳ 2015, at 7:18, Davey Shafik wrote: > > On Tue, Nov 24, 2015 at 1:00 AM, Sebastian Bergmann > wrote: > >>> On 11/23/2015 10:10 PM, Anatol Belski wrote: >>> >>> c) do RC8, release on 3rd, expect there are no bugs come in >> >> +1 > > > +1 +1

Re: [PHP-DEV] 7.0.0 release

On 23.11.2015, at 22:10, Anatol Belski wrote: > So in the end, a solution is wanted. I don't think any opinion is allowed to > be ignored for such a topic. So options > > a) release on 26th including all known bug fixes > b) do RC8, assume there are no bugs, so target 10th

Re: [PHP-DEV] 7.0.0 release

On Mon, Nov 23, 2015 at 11:45 PM, Good guy wrote: > On 23/11/2015 21:10, Anatol Belski wrote: > >> Hi, >> >> it is sad to see that the discussion went in the direction it went, but >> I'm glad to have missed that being away all day and at the end of it >> realizing my mail

Re: [PHP-DEV] 7.0.0 release

Good guy in php.internals (Mon, 23 Nov 2015 22:45:38 +): >when is it available from Windows binaries download site? It still says >this: > >7 has no release 7 has no release, but RC7 is here: http://windows.php.net/qa/ -- Jan -- PHP

Re: [PHP-DEV] Re: Resource typehint and return type

Ben Scholzen 'DASPRiD' wrote on 23/11/2015 01:57: On 13.11.2015 12:59, Bob Weinand wrote: The alternative is replacing the resources by proper objects, without methods and public properties. Then we could integrate it into our object hierarchy in a very lightweight way with proper typing.

Re: [PHP-DEV] INDRECT in arrays causes count() to become unpredictable

Zeev, On Mon, Nov 23, 2015 at 9:43 AM, Zeev Suraski wrote: > > >> On 23 בנוב׳ 2015, at 15:21, Anthony Ferrara wrote: >> >> Zeev and all, >> >>> On Mon, Nov 23, 2015 at 9:05 AM, Zeev Suraski wrote: >>> >>> No, but both the seriousness of the

Re: [PHP-DEV] INDRECT in arrays causes count() to become unpredictable

> Am 23.11.2015 um 15:52 schrieb Rasmus Lerdorf : > >> On Nov 23, 2015, at 15:21, Anthony Ferrara wrote: >> >> Rasmus, >> >>> I think this was mostly a PR failure on my part actually. If I/we are a bit >>> more careful about how we handle similar

Re: [PHP-DEV] Re: Resource typehint and return type

Hi, On Mon, Nov 23, 2015 at 10:30 AM, Rowan Collins wrote: > Ben Scholzen 'DASPRiD' wrote on 23/11/2015 01:57: > >> On 13.11.2015 12:59, Bob Weinand wrote: >> >>> The alternative is replacing the resources by proper objects, without >>> methods and public properties.

Re: [PHP-DEV] INDRECT in arrays causes count() to become unpredictable

On Sun, Nov 22, 2015 at 11:08 PM, Rasmus Lerdorf wrote: > On 11/23/2015 09:49 AM, Phil Sturgeon wrote: >> The "There will always be bugs" argument is a strawman, nobody is >> saying wait until it's perfect. >> >> People in this thread are consistently conflating "there will

Re: [PHP-DEV] Re: Resource typehint and return type

On 23.11.2015 16:30, Rowan Collins wrote: I believe the blocker on just rushing to convert existing resources into objects is that there are functions like is_resource() and getttype() which will start behaving differently. There's another blocker: the SplFileObject currently has no fclose()

Re: [PHP-DEV] Re: Resource typehint and return type

Davey Shafik wrote on 23/11/2015 16:17: How is this a breaking change? The only way you can get a resource, or resource-object is from a function that currently returns a resource (e.g. imagecreate()), and you can't do anything with a resource except pass into things that expect resources.

Re: [PHP-DEV] INDRECT in arrays causes count() to become unpredictable

The conversation is STILL not about the severity of the bug, it's now about playing the blame game of whose fault this is that PR got bad, that people are being meanies to those that are working hard (not true) and repeating the same mantra over and over again: > I still don't see anyone going

Re: [PHP-DEV] INDRECT in arrays causes count() to become unpredictable

On Nov 23, 2015, at 15:21, Anthony Ferrara wrote: > > Rasmus, > >> I think this was mostly a PR failure on my part actually. If I/we are a bit >> more careful about how we handle similar issues and the people lurking with >> itchy Twitter trigger fingers would spend a bit

Re: [PHP-DEV] INDRECT in arrays causes count() to become unpredictable

> On 23 בנוב׳ 2015, at 15:51, Rasmus Lerdorf wrote: > >> On Nov 23, 2015, at 15:21, Anthony Ferrara wrote: >> >> Rasmus, >> >>> I think this was mostly a PR failure on my part actually. If I/we are a bit >>> more careful about how we handle similar

Re: [PHP-DEV] PHP7 Coalesce operator

Well use null coalesce + elvis together then? // Coalesce possible null values, and use truthy comparison in elvis to "coalesce" to a default $var = ($_GET['possible_value'] ?? $_COOKIE['secondary'] ?? false) ?: DEFAULTS['var']; On Mon, Nov 23, 2015 at 1:16 PM, shadda wrote:

Re: [PHP-DEV] PHP7 Coalesce operator

That’s not a bad idea, but it’s still limited in certain cases, where your list of possibles is, lets say, complex. At this point, I think you guys get what I’m after, and I’m wondering if anyone else finds the idea as useful I as do. In fact, if it didn’t break the One Law of PHP (thou shalt

[PHP-DEV] 7.0.0 release

Hi, it is sad to see that the discussion went in the direction it went, but I'm glad to have missed that being away all day and at the end of it realizing my mail server messed up. Please lets get the tone down and discuss factually! I would like to turn back to the point I was depicting in my

Re: [PHP-DEV] 7.0.0 release

Hi! > So in the end, a solution is wanted. I don't think any opinion is > allowed to be ignored for such a topic. So options > > a) release on 26th including all known bug fixes > b) do RC8, assume there are no bugs, so target 10th for RTM > c) do RC8, release on 3rd, expect there are no bugs

Re: [PHP-DEV] 7.0.0 release

On November 23, 2015 10:10:37 PM GMT+01:00, Anatol Belski wrote: >Hi, > >it is sad to see that the discussion went in the direction it went, but >I'm glad to have missed that being away all day and at the end of it >realizing my mail server messed up. Please lets get the