Re: [PHP-DEV] 8.0 Feature Freeze in 4 weeks

On Tue, Jul 21, 2020 at 4:47 PM Sara Golemon wrote: > On Tue, Jul 21, 2020 at 9:29 AM Nikita Popov wrote: > > > Just so people aren't surprised, I plan to start landing implementations > > for RFCs that are likely to be accepted in advance of the actual vote > > closure, as we have many RFC vote

[PHP-DEV] Re: [RFC][Discussion] Objects can be declared falsifiable

Learning more everyday. This thread will be the “official thread” - other related threads have been added to the RFC (including one from 11 years ago): https://bit.ly/php-0002-rfc Created fork - with PR on fork to explore and leave notes without hitting the mailing

Re: [PHP-DEV] 8.0 Feature Freeze in 4 weeks

On Tue, Jul 21, 2020 at 9:29 AM Nikita Popov wrote: > Just so people aren't surprised, I plan to start landing implementations > for RFCs that are likely to be accepted in advance of the actual vote > closure, as we have many RFC votes ending close to feature freeze. Of > course, if something end

Re: [PHP-DEV] 8.0 Feature Freeze in 4 weeks

On Tue, Jul 7, 2020 at 3:49 PM Sara Golemon wrote: > Per the timetable at https://wiki.php.net/todo/php80 , the PHP-8.0 branch > will be cut in FOUR WEEKS on Aug 4th just prior to the release of > php-8.0.0beta1 on Aug 6th. > Please note that August 4th marks FEATURE FREEZE for 8.0. > > All RFCs

[PHP-DEV] [VOTE] Don't automatically unserialize Phar metadata outside getMetadata()

Hi internals, I've started the vote on https://wiki.php.net/rfc/phar_stop_autoloading_metadata as announced earlier in https://externals.io/message/110871 ([RFC] Don't automatically unserialize Phar metadata outside getMetadata()) This adds the mitigations described in https://externals.io/messa

Re: [PHP-DEV] [RFC] \PHP namespace usage heuristics

On Tue, Jul 21, 2020, at 3:31 AM, Rowan Tommins wrote: > On Tue, 21 Jul 2020 at 01:36, Mark Randall wrote: > > > So either you fake namespaces e.g. PhpToken or you trample on userland > > \Tokenizer. > > > > > While you're making a reasonable point, I really wish people would stop > using that

[PHP-DEV] [RFC][VOTE] debug_backtrace alternative as an array of StackFrame objects

Hi Internals, I've opened the voting for adding object-based debug_backtrace() alternative. Secondary vote is about replacing object-based trace for Throwable::getTrace(). Voting opened 2020-07-21 and closes 2020-08-04. Link to the RFC https://wiki.php.net/rfc/stack-frame-class#vote Cheers, Mic

Re: [PHP-DEV] Re: [RFC][DISCUSSION] debug_backtrace alternative as an array of StackFrame objects

Hi Nikita, wt., 21 lip 2020 o 10:41 Nikita Popov napisał(a): > Why does StackFrame define both public typed properties *and* getter > methods? One or the other would make sense to me, but not both. > TBH I didn't know what should be the preference, but since a StackFrame class is final providin

Re: [PHP-DEV] Re: [RFC][DISCUSSION] debug_backtrace alternative as an array of StackFrame objects

On Tue, Jul 21, 2020 at 7:14 AM Michał Marcin Brzuchalski < michal.brzuchal...@gmail.com> wrote: > wt., 21 lip 2020 o 07:07 tyson andre > napisał(a): > > > > Can you give an example of an internal stack frame? > > > > A stack frame that was created by a PHP internal function instead of by > > use

Re: [PHP-DEV] [RFC] \PHP namespace usage heuristics

On Tue, 21 Jul 2020 at 01:36, Mark Randall wrote: > So either you fake namespaces e.g. PhpToken or you trample on userland > \Tokenizer. > While you're making a reasonable point, I really wish people would stop using that particular class as an example, because I don't think the "PHP" in its na