Re: [PHP-DEV] Vote: Straw poll for P++ feasibility

Hello, if you would drop zend engine as is and the idea behind it (which is most difficult thing to admit and accept), then use llvm-core. Making: -- lexer, parser grammar -- reference counting -- type hint policies -- builtins container -- JITTER for compatibility. -- bytecode -- LLVM bytecode

Re: [PHP-DEV] Vote: Straw poll for P++ feasibility

On 16/08/2019 17:40, Chase Peeler wrote A BC break to clean up the language might be justified in one case, and not in another. To make a blanket statement that we will or will not attempt to clean up the language is not wise in my opinion. It puts the project in a bad place if it's forced to

Re: [PHP-DEV] Vote: Straw poll for P++ feasibility

On Fri, Aug 16, 2019 at 12:08 PM Mark Randall wrote: > On 16/08/2019 11:18, Christoph M. Becker wrote: > > It is not necessarily required to have an implementation for an RFC > > available, see item (6) in . > > I have enormous respect for Derick, but I can't help

Re: [PHP-DEV] Vote: Straw poll for P++ feasibility

On Fri, Aug 16, 2019, 5:08 PM Mark Randall wrote: > On 16/08/2019 11:18, Christoph M. Becker wrote: > > It is not necessarily required to have an implementation for an RFC > > available, see item (6) in . > > I have enormous respect for Derick, but I can't help

Re: [PHP-DEV] Vote: Straw poll for P++ feasibility

On 16/08/2019 11:18, Christoph M. Becker wrote: It is not necessarily required to have an implementation for an RFC available, see item (6) in . I have enormous respect for Derick, but I can't help but feel this "RFC" was bodged from the start. There's

[PHP-DEV] P-- or when less is more

P-- or when less is more Dreaming under the August Sun = 1. Defining a simpler scripting language, basically PHP 5.0 but without type-hints. 2. Developing an interpreter for the scripting language above. Basically, a trimmed-down version of the current interpreter.

Re: [PHP-DEV] Vote: Straw poll for P++ feasibility

On 16.08.2019 at 01:39, Peter Kokot wrote: > Off topic question/request if it's maybe possible and doable unless > I've missed something. Current RFC process is in short something like > writing a text document together with the implementation itself via a > pull request already and at the same