Re: [PHP-DEV] Re: Binary string forward compatibility removal

Morning Andrea, Who is widely deploying something that does absolutely nothing ? The only reason to keep it would be that we are going to change the default representation, as pointed out we're not. This cannot have been left in for considered reasons, it was just forgotten about.

[PHP-DEV] سلام دوست من، طعم يک رفاقت واقعي رو چشيدي ؟

نمي دانم تا به حال با کسي رفيق بوده ايد يا نه، اما طبيعي است که هر کسي در طول زندگي با افراد زيادي ارتباط برقرار مي کند; خواه اين ارتباط قوي و صميمي باشد، خواه ضعيف و در حد يک سلام و احوال پرسي. جالب است و شايد هم باور کردنش خت باشد، اما واقعيت دارد و آن اين که هيچ کسي نيست که به شهداء سلام

[PHP-DEV] Re: Binary string forward compatibility removal

Hi Pedro, I don't support this removal. Currently, yes, the flag doesn't do anything, and it's unlikely to do so in future, as Nikita points out. However, it's not improbable that we might see a `u` flag in future, and if that was added, `b` might still be useful as an explicit counterpart.

[PHP-DEV] Re: [RFC] Interval Comparison

Hi, Fleshgrinder wrote: It is not very readable and repetitive. It would be interesting to support a more mathematical notation for this: ``` if (0 < $x < 42) { echo 'x is in (0, 42)'; } if (0 <= $x <= 42) { echo 'x is in [0, 42]'; } ``` I cannot judge how complicated it is to

Re: [PHP-DEV] OpenSSL - New Defaults

On Sun, Nov 6, 2016 at 2:19 PM, Jakub Zelenka wrote: > Hi, > > On Thu, Nov 3, 2016 at 4:11 PM, Scott Arciszewski > wrote: >> >> Hi, >> >> Can we change openssl_public_encrypt() and openssl_private_decrypt() from >> defaulting to PKCS1v1.5 padding, in favor of

Re: [PHP-DEV] Binary string forward compatibility removal

On Sun, Nov 6, 2016 at 8:56 PM, François Laupretre wrote: > Hi, > > it was stated during the pre-7 discussions, that this flag would be kept > for possible future unicode-compliant developments. So, people needing > binary strings are still encouraged to use the flag, even if

Re: [PHP-DEV] [RFC] Interval Comparison

On Sun, Nov 6, 2016 at 1:59 PM David Rodrigues wrote: > I guess that the biggest problem is about the code parsing. Currently PHP > should supports what you wrote, but with another meaning. And personally I > think that this feature is not too common on programming

Re: [PHP-DEV] [RFC] Interval Comparison

I guess that the biggest problem is about the code parsing. Currently PHP should supports what you wrote, but with another meaning. And personally I think that this feature is not too common on programming language in general, once that it is possible from first format (maybe more clear too). Em

[PHP-DEV] [RFC] Interval Comparison

Validating whether a number is within a closed or open interval is currently possible only via a construct like the following: ``` if (0 < $x && $x < 42) { echo 'x is in (0, 42)'; } if (0 <= $x && $x <= 42) { echo 'x is in [0, 42]'; } ``` It is not very readable and repetitive. It would

Re: [PHP-DEV] Binary string forward compatibility removal

Hi, it was stated during the pre-7 discussions, that this flag would be kept for possible future unicode-compliant developments. So, people needing binary strings are still encouraged to use the flag, even if it is not used in the current versions. Regards François Le 06/11/2016 à 20:22,

Re: [PHP-DEV] OpenSSL - New Defaults

2016-11-06 20:19 GMT+01:00 Jakub Zelenka : > Hi, > > On Thu, Nov 3, 2016 at 4:11 PM, Scott Arciszewski > wrote: > > > Hi, > > > > Can we change openssl_public_encrypt() and openssl_private_decrypt() from > > defaulting to PKCS1v1.5 padding, in favor of

[PHP-DEV] Binary string forward compatibility removal

Hi internals, I've created a PR (https://github.com/php/php-src/pull/2187) aiming at the removal of the binary string forward compatibility. Reproducing the description of the PR: In version 5.2.1, the b prefix and the (binary) cast were introduced for forward compatibility with the

Re: [PHP-DEV] OpenSSL - New Defaults

Hi, On Thu, Nov 3, 2016 at 4:11 PM, Scott Arciszewski wrote: > Hi, > > Can we change openssl_public_encrypt() and openssl_private_decrypt() from > defaulting to PKCS1v1.5 padding, in favor of defaulting to OAEP? > > I'll create an RFC for this later. It will just prevent a

[PHP-DEV] [RFC][VOTE] Object typehint

Hi everyone, Two weeks have passed since this RFC was put to discussion here. Therefore, I'm going to put it to a vote for inclusion in PHP 7.2. Voting starts today, 2016-11-06, and will close after two weeks on the Sunday 2016-11-20 at midnight. The RFC and voting widget can be found here:

Re: [PHP-DEV] Security issue handling

On Sat, 5 Nov 2016 at 19:13 Stanislav Malyshev wrote: > Hi! > > > On 24/10/2016 07:16, Stanislav Malyshev wrote: > >> c. Get some specific people to volunteer to review patches in security > >> repo regularly - how? Any takers? > > > > I'd be happy to help with reviewing and