Re: [PHP-DEV] PHP 7.2 forked

On Sat, Jul 22, 2017 at 12:48 PM, Nikita Popov wrote: > What's out current state regarding ABI? I've recently done some work on > making mbstring slightly less abysmally slow, but landed the changes on > master only, because this included ABI breaks in mbfl/mbstring APIs and

RE: [PHP-DEV] PHP 7.2 forked

Hi Nikita, > -Original Message- > From: Nikita Popov [mailto:nikita@gmail.com] > Sent: Saturday, July 22, 2017 6:48 PM > To: Sara Golemon > Cc: PHP internals > Subject: Re: [PHP-DEV] PHP 7.2 forked > > On Tue, Jul 18, 2017 at 4:48 PM, Sara

Re: [PHP-DEV] Re: PHP 7.2.0 Beta 1 released

Rasmus Lerdorf in php.internals (Sat, 22 Jul 2017 09:22:07 -0400): >Ok, so it is a normal E_WARNING and not the source of the fatal error you >hit. You must have something else going on. Perhaps a custom error handler >turning it into a fatal, although that also hasn't changed from 7.1. Drupal7

Re: [PHP-DEV] PHP 7.2 forked

2017-07-22 18:48 GMT+02:00 Nikita Popov : > What's out current state regarding ABI? I've recently done some work on > making mbstring slightly less abysmally slow, but landed the changes on > master only, because this included ABI breaks in mbfl/mbstring APIs and > globals.

Re: [PHP-DEV] PHP 7.2 forked

On Tue, Jul 18, 2017 at 4:48 PM, Sara Golemon wrote: > That's it! Feature freeze is on. > > Please include branch PHP-7.2 in all merges from 7.1 and earlier. > Please commit all 7.2 fixes to PHP-7.2 and merge to master which is > now targetting 7.3 > > This is real.

[PHP-DEV] Request for karma

Hi, I registered my wiki account "Blar" and need some karma for my first RFC for new cookie functions. I already posted some infos about "http_cookie_set and http_cookie_remove" on the mailinglist. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit:

Re: [PHP-DEV] Re: PHP 7.2.0 Beta 1 released

On Sat, Jul 22, 2017 at 8:21 AM, Jan Ehrhardt wrote: > I am sure I am running PHP 7, not sure it is E_STRICT in 7.0 & 7.1. Just > misread > your statement "Even in 5.6 and 5.5 it was an E_STRICT", I suppose. > > With the 80-character line-breaks: > >

Re: [PHP-DEV] Re: PHP 7.2.0 Beta 1 released

Rasmus Lerdorf in php.internals (Sat, 22 Jul 2017 08:07:55 -0400): >On Sat, Jul 22, 2017 at 12:32 AM, Jan Ehrhardt wrote: > >> Your example issues an E_STRICT warning, in both PHP 7.2 nts x64 and PHP >> 7.1 nts x64, so it must be caused by something else. > >Are you sure you

[PHP-DEV] Status of thread safety in PHP 7.0 & 7.1 ZTS?

Quoting https://twitter.com/krakjoe/status/887743571515912196 >Just FYI ... Thread safety in PHP 7.0 and 7.1 is broken: If you are >using ZTS upgrade to 7.2 ... peril awaits those who ignore this warning Should we ditch PHP 7.0 ZTS and PHP 7.1 ZTS? I ran into this while discussing the pthreads

Re: [PHP-DEV] Re: PHP 7.2.0 Beta 1 released

On Sat, Jul 22, 2017 at 12:32 AM, Jan Ehrhardt wrote: > Your example issues an E_STRICT warning, in both PHP 7.2 nts x64 and PHP > 7.1 nts x64, so it must be caused by something else. Are you sure you are even running PHP 7? This type of code hasn't issued an E_STRICT since

[PHP-DEV] Pass-through object operator

Hello Internals! I'd like to gauge a reaction on a potential RFC proposal. As per the RFC howto, I shall state that this would be a "concept" as I don't have anyone lined up that would implement the feature, and I'm not a C dev myself. (Though if no one volunteers I may take this as a learning

[PHP-DEV] oh my god -> Re: [PHP-DEV] PHP 7.2.0 is broken since the first alpha -> opcache backtrace

i would say that is pretty one of the biggest major bugs i have ever seen because as you can see here even that single code snippet alone is enough and the variable $cms_https_only is explicitly set to 0 the line before even if you change it to if($cms_https_only === 1 &&