Re: [PHP-DEV] [RFC] Pipe Operator, take 2

2021-06-07 Thread Eugene Leonovich
will fail if you pass only one: https://3v4l.org/tLO0s. I wonder what the correct version of the pipe example (the one that uses strings as callbacks) would look like, given that you have to pass two arguments for explode()? -- Thank you and best regards, Eugene Leonovich

Re: [PHP-DEV] Re: Error instead of returning false

2019-05-07 Thread Eugene Leonovich
On Tue, May 7, 2019 at 5:14 PM Mark Randall wrote: > On 07/05/2019 15:22, Gert wrote: > > My idea, extremely summarized, would be to take the functions that > > return false/null when they 'error', and instead make them actually > > throw an error. > > It comes up on various discussion forums eve

Re: [PHP-DEV] [RFC] JIT

2019-02-13 Thread Eugene Leonovich
: https://gist.github.com/rybakit/bb551f962b706a9e08c995cf5ed9762f -- Thank you and best regards, Eugene Leonovich

Re: [PHP-DEV] [RFC] JIT

2019-02-04 Thread Eugene Leonovich
On Mon, Feb 4, 2019 at 3:45 PM Zeev Suraski wrote: > One our hopes in opening this up for comments, is that people would > actually try the code themselves and experiment with it - well beyond what > we can do ourselves. > Is there a docker image with JIT support that people can try?

Re: [PHP-DEV] Add is_vectorlike($array) function

2017-05-06 Thread Eugene Leonovich
s/maps: https://github.com/rybakit/msgpack.php/blob/master/src/Packer.php#L112-L114 -- Thank you and best regards, Eugene Leonovich

Re: [PHP-DEV] New escaped output operator

2016-07-01 Thread Eugene Leonovich
On Fri, Jul 1, 2016 at 10:51 AM, Михаил Востриков < michael.vostri...@gmail.com> wrote: > > I can easier add a new template to e.g. a Laravel > > project (own parser, own extension, living next to existing blade > templates) > > Your project already has a template engine, and framework has common

[PHP-DEV] Re: New Feature: Fully qualified class name resolution as scalar with class keyword

2012-07-13 Thread Eugene Leonovich
I'm a bit confused by the "class" keyword in the syntax ClassName::class. We already have the magic constant __CLASS__ which does exactly the same class name resolving, if you refer it within the class. So why to introduce a new keyword instead of using __CLASS__, like ClassName::__CLASS__? Eug