Re: [PHP-DEV] PHP 7.1 - Address PHPSadness #28?

Craig Francis wrote on 14/09/2015 12:46: So yes, in the example above, an isset() would work, but I was trying to show why I don't think it's odd to "suppress a warning for a plain variable" when it does not exist. Yes, and I agree that this example shows a reasonable use of isset(). It

[PHP-DEV] Bumping minimal OpenSSL version to 0.9.8

Hi, At the moment the minimal OpenSSL version is 0.9.6. I realised yesterday that there are some types changes between 0.9.7 and 0.9.8 that would have to be address in overflow checks (EVP_DigestUpdate and related). I also noticed that 0.9.6 might not even compile without warnings as it's

[PHP-DEV] Re: [PHP-CVS] com php-src: Added an experemental ability to move PHP code pages (PHP TEXT segment) into HUGE pages. PHP should be configured and built with --enable-huge-code-pages, OS shoul

The effect of this patch is really exiting to keep it disabled by default... :) $ perf stat -e instructions,iTLB-loads,iTLB-load-misses,cycles sapi/cgi/php-cgi -d opcache.enable_huge_code_pages=0 -T 1 /var/www/html/bench/wordpress-3.6/index.php > /dev/null 191,778,620,621

[PHP-DEV] Re: [PHP-CVS] com php-src: Added an experemental ability to move PHP code pages (PHP TEXT segment) into HUGE pages. PHP should be configured and built with --enable-huge-code-pages, OS shoul

Hey: On Mon, Sep 14, 2015 at 6:57 PM, Dmitry Stogov wrote: > The effect of this patch is really exiting to keep it disabled by default... > :) > > $ perf stat -e instructions,iTLB-loads,iTLB-load-misses,cycles > sapi/cgi/php-cgi -d opcache.enable_huge_code_pages=0 -T 1 >

Re: [PHP-DEV] PHP 7.1 - Address PHPSadness #28?

On 9 Sep 2015, at 19:34, Rowan Collins wrote: > Craig Francis wrote on 09/09/2015 16:54: >> I don't think it is an odd thing to suppress a warning for a plain variable. >> >> For example, on a blog you may have a list of articles, which is used by >> both the admin

Re: [PHP-DEV] PHP 7.1 - Address PHPSadness #28?

Craig Francis wrote on 14/09/2015 16:57: Hi Rowan, I think I've said everything I can from my point of view (and my understanding of how other developers see and use the isset function). And that's not to say I disagree with what your saying Rowan, I'm just voicing my view that I think a

Re: [PHP-DEV] PHP 7.1 - Address PHPSadness #28?

Hi Rowan, I think I've said everything I can from my point of view (and my understanding of how other developers see and use the isset function). And that's not to say I disagree with what your saying Rowan, I'm just voicing my view that I think a language with exists() would be nicer than the

Re: [PHP-DEV] PHP 7.1 - Address PHPSadness #28?

Hi! > I’m not sure what a good solution is, however. Changing isset() > will have consequences: making it return true for null will > magically fix a No. There's no reason for null to exist if isset returns true on null. If one doesn't understand that, one should not be using null at all. --

Re: [PHP-DEV] taint

> On Sep 14, 2015, at 1:35 PM, Kalle Sommer Nielsen wrote: > > Hi Christopher > > 2015-09-14 4:44 GMT+02:00 Christopher Owen : >> Please consider making ‘taint’ a first-class feature/extension in PHP 7.0. > > It is way too late for any extension to be

RE: [PHP-DEV] Re: [PHP-CVS] com php-src: Added an experemental ability to move PHP code pages (PHP TEXT segment) into HUGE pages. PHP should be configured and built with --enable-huge-code-pages, OS s

> -Original Message- > From: Dmitry Stogov [mailto:dmi...@zend.com] > Sent: Monday, September 14, 2015 10:37 PM > To: Anatol Belski > Cc: Anatol Belski ; Kalle Sommer Nielsen ; > Rasmus Lerdorf ; Xinchen Hui

Re: [PHP-DEV] Suggestion: Adding PUT, PATCH and DELETE

I've read some of the earlier discussion (not all, require sleep will read more tomorrow). To be clear I don't want to start a naming discussion again. If we have a new name for $_POST or not isn't the main focus of this PR. I want to allow PUT, PATCH and DELETE and handle them the same way as

Re: [PHP-DEV] PHP 7.1 - Address PHPSadness #28?

Hi! >> No. There's no reason for null to exist if isset returns true on >> null. If one doesn't understand that, one should not be using >> null at all. > > > Nonsense. Oh, thank you! That's a good start for a polite argument. > It just means that one isn’t using null the way you do. No, it

Re: [PHP-DEV] Suggestion: Adding PUT, PATCH and DELETE

+1 Yes, it is useful to have in the PHP core. Possible names: $_BODY, $_DATA, $_INPUT, $_REQUEST -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DEV] Suggestion: Adding PUT, PATCH and DELETE

On Mon, Sep 14, 2015 at 3:22 PM, Daniel Persson wrote: > Hi. > > I've not been a member for too long so I might have missed if this have > been discussed earlier. > > But I've created a small PR to the basic request handling to support PUT, > PATCH and DELETE. > >

RE: [PHP-DEV] Bumping minimal OpenSSL version to 0.9.8

Hi Jakub, > -Original Message- > From: jakub@gmail.com [mailto:jakub@gmail.com] On Behalf Of Jakub > Zelenka > Sent: Monday, September 14, 2015 2:04 PM > To: PHP internals list ; Anatol Belski > > Subject: [PHP-DEV] Bumping minimal

[PHP-DEV] Suggestion: Adding PUT, PATCH and DELETE

Hi. I've not been a member for too long so I might have missed if this have been discussed earlier. But I've created a small PR to the basic request handling to support PUT, PATCH and DELETE. https://github.com/php/php-src/pull/1519 Summary: Added support for request methods with the smallest

Re: [PHP-DEV] PHP 7.1 - Address PHPSadness #28?

Le 14/09/2015 22:17, Robert Williams a écrit : I’m not sure what a good solution is, however. Changing isset() will have consequences: making it return true for null will magically fix a lot of bugs out there, but it’ll also break code where the programmer understood how it really works. Adding

Re: [PHP-DEV] Re: [PHP-CVS] com php-src: Added an experemental ability to move PHP code pages (PHP TEXT segment) into HUGE pages. PHP should be configured and built with --enable-huge-code-pages, OS s

On 09/14/2015 02:13 PM, Anatol Belski wrote: > > >> -Original Message- >> From: Dmitry Stogov [mailto:dmi...@zend.com] >> Sent: Monday, September 14, 2015 10:37 PM >> To: Anatol Belski >> Cc: Anatol Belski ; Kalle Sommer Nielsen ; >>

[PHP-DEV] HTTP/2 Server Push support in ext/curl

Hey all, I'm trying to work up a patch for ext/perl to allow the CURLMOPT_PUSHFUNCTION and CURLMOPT_PUSHDATA options, which allow for HTTP/2 Server Push. PUSHFUNCTION allow you to register a callback that can accept/reject an HTTP/2 server push by returning either CURL_PUSH_OK (0), or

[PHP-DEV] PHP-7.0 branched

Hi, As was announced a couple of months ago, PHP 7.0 should get its own branch when PHP 5.4 goes EOL. 5.4 has reached its EOL today, thus PHP-7.0 was just branched out. This means, it turns back to the usual commit workflow. As of now, any patches targeting 7.0 have to be merged into PHP-7.0

Re: [PHP-DEV] PHP 7.1 - Address PHPSadness #28?

I really don’t understand the resistance to this type of change, other than knowing that a fix will necessarily be messy. The fact is, PHP distinguishes between a variable that has been declared but defined to null and one that hasn’t been declared. The value of the first may safely be

Re: [PHP-DEV] Re: [PHP-CVS] com php-src: Added an experemental ability to move PHP code pages (PHP TEXT segment) into HUGE pages. PHP should be configured and built with --enable-huge-code-pages, OS s

On Mon, Sep 14, 2015 at 11:05 PM, Anatol Belski wrote: > Hi Dmitry, > > > -Original Message- > > From: Dmitry Stogov [mailto:dmi...@zend.com] > > Sent: Monday, September 14, 2015 12:58 PM > > To: Anatol Belski ; Kalle Sommer Nielsen ; >

Re: [PHP-DEV] PHP 7.1 - Address PHPSadness #28?

On Sep 14, 2015, at 13:23, Stanislav Malyshev wrote: > > No. There's no reason for null to exist if isset returns true on null. > If one doesn't understand that, one should not be using null at all. Nonsense. It just means that one isn’t using null the way you do. You’re

[PHP-DEV] Benchmark Results for PHP Master 2015-09-14

Results for project php-src-nightly, build date 2015-09-14 05:00:00+03:00 commit: fe08b933e4ab380d4b07275384226b688f82eeac revision_date: 2015-09-13 12:35:35+02:00 environment:Haswell-EP cpu:Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz 2x18 cores, stepping 2, LLC 45

[PHP-DEV] taint

Please consider making ‘taint’ a first-class feature/extension in PHP 7.0. https://pecl.php.net/package/taint Christopher Owen.

[PHP-DEV] Introduction

Hello PHP Internals. I would like to introduce myself in order to validate a wiki account for the purposes of proposing an RFC. Thank you for reading this note. Regards, Christopher Owen. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit:

RE: [PHP-DEV] Re: [PHP-CVS] com php-src: Added an experemental ability to move PHP code pages (PHP TEXT segment) into HUGE pages. PHP should be configured and built with --enable-huge-code-pages, OS s

Hi Dmitry, > -Original Message- > From: Dmitry Stogov [mailto:dmi...@zend.com] > Sent: Monday, September 14, 2015 12:58 PM > To: Anatol Belski ; Kalle Sommer Nielsen ; > Rasmus Lerdorf ; Xinchen Hui ; > Nikita Popov

Re: [PHP-DEV] taint

Hi Christopher 2015-09-14 4:44 GMT+02:00 Christopher Owen : > Please consider making ‘taint’ a first-class feature/extension in PHP 7.0. It is way too late for any extension to be included in the 7.0 release now, but you can write an RFC targetting 7.1, please see the