RE: [PHP-DEV] Lazy keys comparison during hash lookups

> -Original Message- > From: Andone, Bogdan [mailto:bogdan.and...@intel.com] > Sent: Tuesday, March 08, 2016 4:19 PM > To: 'Nikita Popov' > Cc: internals@lists.php.net > Subject: RE: [PHP-DEV] Lazy keys comparison during hash lookups > > > From: Nikita Popov

Re: [PHP-DEV] [RFC Discussion] Catching multiple exception types

Hi :) I think it is feature that is useful time to time, not very often. One example: class PackingFailed extends \Exception implements PackagingException {} // this exception could originate from package with assertions/exceptions, // so I cannot use common interface with above class EmptyName

[PHP-DEV] PHP Docbook, documentation of LDAP extension

Hello, Someone opened a bug complaining about documentation not stating that ldap_sort is deprecated in PHP7: https://bugs.php.net/bug.php?id=71490 So I go to the ldap_sort documentation page, clic on edit, and it says it has been modified by Andreas Heigl, and indeed it contains the

Re: [PHP-DEV] [RFC Discussion] Catching multiple exception types

Hi Björn, The only time I had to do this with core PHP exceptions is to make the code compatible for both PHP5 and PHP7: try { } catch(\Exceptions $e) { } catch(\Throwable $e) { } But it will of course not be applicable since this feature is targeting PHP7.1. Other than that the PHP core

[PHP-DEV] Can you please give me karma? Understanding Karma as a Buddhist

Hello, You remember my question? A question about null coalescing operator.. $this->request->data['comments']['user_id'] = $this->request->data['comments']['user_id'] ?? ‘value’; … And you remember my pull request? https://github.com/php/php-src/pull/1795

Re: [PHP-DEV] [RFC Discussion] Catching multiple exception types

Den 2016-03-08 kl. 22:42, skrev Pierrick Charron: Hi internals, Bronisław Białek and I would like to start a discussion about allowing multiple exception types to be caught in a single catch statement. https://wiki.php.net/rfc/multiple-catch A working implementation and tests are available in

Re: [PHP-DEV] [RFC Proposal] var keyword deprecation/removal

> > > That we should definitely avoid. I do not consider the *var* keyword > being a discussion about coding style preferences---this decision was > already made in PHP 5! The *public* keyword was introduced and it > superseded the *var* keyword including an E_STRICT error. Hence, this >

Re: [PHP-DEV] [RFC Discussion] Catching multiple exception types

Hi Sean and Yasuo I agree that they are somehow related, but I also think (and I might be wrong) that the behaviour of the Multi-Catch is obvious and I don't see how this syntax/feature could be interpreted otherwise. The multi-catch don't have any open-issue that the Union-Types have like weak

Re: [PHP-DEV] [RFC Discussion] Catching multiple exception types

Hi all, On Wed, Mar 9, 2016 at 6:50 AM, Sean DuBois wrote: > It may be an issue that this is close in design to [0] union types. > This RFC would be *great* for code quality, just might be a subset of > union types. > > thanks > > [0] https://wiki.php.net/rfc/union_types Nice

Re: [PHP-DEV] [RFC Discussion] Catching multiple exception types

On Tue, Mar 08, 2016 at 04:42:29PM -0500, Pierrick Charron wrote: > Hi internals, > > Bronisław Białek and I would like to start a discussion about allowing > multiple exception types to be caught in a single catch statement. > > https://wiki.php.net/rfc/multiple-catch > > A working implementation

[PHP-DEV] [RFC Discussion] Catching multiple exception types

Hi internals, Bronisław Białek and I would like to start a discussion about allowing multiple exception types to be caught in a single catch statement. https://wiki.php.net/rfc/multiple-catch A working implementation and tests are available in the RFC. We are waiting for your constructive

Re: [PHP-DEV] Equal Null coalescing operator ??= https://github.com/php/php-src/pull/1795

On Tue, Mar 8, 2016 at 9:59 AM, Midori Kocak wrote: > > $this->request->data['comments']['user_id'] = > $this->request->data['comments']['user_id'] ?? ‘value’; > $this->request->data['comments']['user_id’] ??= ‘value’; > RFC it so there's a proper vote process, but you've got

Re: [PHP-DEV] [RFC Proposal] var keyword deprecation/removal

@Tony Marston: I feel directly attacked and offended and others have the feeling too, that is the definition of an insult. That being said, I am staying constructive the whole time and do not avoid communication with you or anyone else because I think we are discussing an important topic. BUT! As

Re: [PHP-DEV] Equal Null coalescing operator ??= https://github.com/php/php-src/pull/1795

On 3/8/2016 6:59 PM, Midori Kocak wrote: > Remember my question? > > $this->request->data['comments']['user_id'] = > $this->request->data['comments']['user_id'] ?? ‘value’; > > I want to check if some var is null and if the same var is null set the same > var to ‘value’. > > Hence I am

Re: [PHP-DEV] Equal Null coalescing operator ??= https://github.com/php/php-src/pull/1795

On 3/8/16 11:59 AM, Midori Kocak wrote: Remember my question? $this->request->data['comments']['user_id'] = $this->request->data['comments']['user_id'] ?? ‘value’; I want to check if some var is null and if the same var is null set the same var to ‘value’. Hence I am repeating the same

Re: [PHP-DEV] [RFC Proposal] var keyword deprecation/removal

TRIMMING TO COMPENSATE FOR TOP POSTING On 08/03/16 17:19, Andrew Brown wrote: > the main argument against removing var that I continue to hear is that 'my > old code won't work anymore because of this unnecessary BC break'. but the > thing is, your code *will* continue to work. unless *you

[PHP-DEV] Equal Null coalescing operator ??= https://github.com/php/php-src/pull/1795

Remember my question? $this->request->data['comments']['user_id'] = $this->request->data['comments']['user_id'] ?? ‘value’; I want to check if some var is null and if the same var is null set the same var to ‘value’. Hence I am repeating the same variable after the equal operator, this does

Re: [PHP-DEV] [RFC Proposal] var keyword deprecation/removal

the main argument against removing var that I continue to hear is that 'my old code won't work anymore because of this unnecessary BC break'. but the thing is, your code *will* continue to work. unless *you choose* to upgrade your PHP version. if you stay on the current major version, it will

[PHP-DEV] BAD Benchmark Results for PHP Master 2016-03-08

Results for project PHP master, build date 2016-03-08 17:20:10+02:00 commit: 58c82ff previous commit:35b34d7 revision date: 2016-03-08 13:16:46+01:00 environment:Haswell-EP cpu:Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz 2x18 cores, stepping 2, LLC 45 MB

[PHP-DEV] Equal Null Coalescing Operator

A question about null coalescing operator.. $this->request->data['comments']['user_id'] = $this->request->data['comments']['user_id'] ?? ‘value’; I want to check if some var is null and if the same var is null set the same var to ‘value’. Hence I am repeating the same variable after the equal

[PHP-DEV] Re: Enabling opcache causes libraries to build as static

Hi, David Zuelke wrote: Is this intentional? Related to opcache's "can only be built shared" status? But why would that trigger static builds? Or is it a bug? While we're at it, why is Opcache still built as shared? Does something prevent it being statically-linked? Thanks. -- Andrea

RE: [PHP-DEV] Lazy keys comparison during hash lookups

> From: Nikita Popov [mailto:nikita@gmail.com] > Sent: Tuesday, March 08, 2016 3:43 PM > To: Andone, Bogdan > Cc: internals@lists.php.net > Subject: Re: [PHP-DEV] Lazy keys comparison during hash lookups > >On Tue, Mar 8, 2016 at 2:18 PM, Nikita Popov wrote: > >> On

Re: [PHP-DEV] Lazy keys comparison during hash lookups

On Tue, Mar 8, 2016 at 2:18 PM, Nikita Popov wrote: > On Tue, Mar 8, 2016 at 2:01 PM, Andone, Bogdan > wrote: > >> Hi Guys, >> >> I would like to propose a small change into the DJBX33A hash function >> algorithm which will make easier the key

Re: [PHP-DEV] Lazy keys comparison during hash lookups

On Tue, Mar 8, 2016 at 2:01 PM, Andone, Bogdan wrote: > Hi Guys, > > I would like to propose a small change into the DJBX33A hash function > algorithm which will make easier the key matching validations in hash > lookup functions. > > The change addresses the modulo 8

Re: [PHP-DEV] [RFC Proposal] var keyword deprecation/removal

On 08/03/16 10:12, Tony Marston wrote: > > The only thing I am learning here is that there are too many cooks > spoiling the broth. There are too many people who want to change the > language into something it was not meant to be. There are too many > people who have this notion of language

[PHP-DEV] Lazy keys comparison during hash lookups

Hi Guys, I would like to propose a small change into the DJBX33A hash function algorithm which will make easier the key matching validations in hash lookup functions. The change addresses the modulo 8 tailing bytes of the key. For these bytes we can use an 8 bit shift instead of a 5 bit

[PHP-DEV] Midori Kocak

A question about null coalescing operator.. $this->request->data['comments']['user_id'] = $this->request->data['comments']['user_id'] ?? ‘value’; I want to check if some var is null and if the same var is null set the same var to ‘value’. Hence I am repeating the same variable after the equal

Re: [PHP-DEV] [RFC Proposal] var keyword deprecation/removal

Tony Marston wrote on 08/03/2016 09:51: a "Rowan Collins" wrote in message news:56dd64f5.5010...@gmail.com... Tony Marston wrote on 07/03/2016 09:14: That takes brains and discipline, something which appears to be lacking in the PHP community. [...] just because some numpty decides [...]

Re: [PHP-DEV] [RFC Proposal] var keyword deprecation/removal

wrote in message news:56ddef7b.6080...@fleshgrinder.com... On 3/7/2016 10:14 AM, Tony Marston wrote: [...] Mind you, those languages were maintained by groups of competent professionals and not an army of chimpanzees. I will not reply fully to your last message because it was yet again

Re: [PHP-DEV] [RFC Proposal] var keyword deprecation/removal

"Walter Parker" wrote in message news:CAMPTd_BvX-vcnm5UejW8B_162AVmVx_+9a=epzx3yn5hz5d...@mail.gmail.com... On Mon, Mar 7, 2016 at 4:27 AM, wrote: > Change for the sake of change is bad, no argument there. Change for the > sake of progress is not and totally normal.

Re: [PHP-DEV] [RFC Proposal] var keyword deprecation/removal

a "Rowan Collins" wrote in message news:56dd64f5.5010...@gmail.com... Tony Marston wrote on 07/03/2016 09:14: That takes brains and discipline, something which appears to be lacking in the PHP community. [...] just because some numpty decides [...] groups of competent professionals and not

Re: [PHP-DEV] [RFC Proposal] var keyword deprecation/removal

"Rowan Collins" wrote in message news:56dd68c0.1090...@gmail.com... Tony Marston wrote on 06/03/2016 08:59: I have worked with two other languages for over a decade each, and as these languages were maintained by "professionals" they could guarantee that code written on day 1 of the first