Re: [PHP-DEV] PHP 5.5.38 is released

2016-07-22 Thread Davey Shafik
Thank you Julien and David for your hard work and a job well done! Congrats! :) - Davey On Fri, Jul 22, 2016 at 8:01 AM, Julien Pauli wrote: > Hi. > > The PHP development team announces the immediate availability of PHP > 5.5.38. > Several security related issues were fixed in this release. Al

Re: [PHP-DEV] [RFC] [Vote] var_info

2016-07-22 Thread Nikita Popov
On Sat, Jul 9, 2016 at 12:19 AM, Stanislav Malyshev wrote: > Hi! > > > Lastly, I'll just leave this list of type-related improvements I'd > actually > > like to see: > > * Make is_object() return true for IncompleteClass. This is just > > ridiculous. I care zero about the theoretical BC impact.

Re: [PHP-DEV] RFC: lazy statements

2016-07-22 Thread David Rodrigues
> However, that also means there's an enormous potential for race > conditions. Technically no more than closures now, but the use cases > seem like they'd make it more prevalent. If you "use" by reference, or > use a mutable object, or a service that depends on IO, etc. then the > resulting valu

Re: [PHP-DEV] [RFC] New operator for context-dependent escaping

2016-07-22 Thread David Rodrigues
The idea is good, but I think that is not pratical in general. --- First point: we should define each new identifier that could be used. It not make clear what this identifier does or even how it should works when a package redefines what it does. For instance: // file1.php set_escape_handler('

Re: [PHP-DEV] [RFC] New operator for context-dependent escaping

2016-07-22 Thread Michael Vostrikov
> I'm conflicted with this one. For you php "More than 90% of output data - is data from DB and must be HTML-encoded." > I have no idea how you came with this, even with applications or websites I'm working on not using a template engine this is far from the truth. > especially now that more ans mo

Re: [PHP-DEV] Pipe Operator v2

2016-07-22 Thread Larry Garfield
On Wed, Jul 20, 2016, at 11:37 PM, Sara Golemon wrote: > > However, the introduction discusses fluent chained methods of objects, and > > states " This RFC aims to improve code readability by bringing fluent > > expressions to functional and OOP libraries not originally designed for the > > task."

Re: [PHP-DEV] RFC: lazy statements

2016-07-22 Thread Larry Garfield
On Thu, Jul 21, 2016, at 10:51 AM, David Rodrigues wrote: > This Feature Request is about the implementation of lazy statements. > > Basically it should implements a 'lazy' keyword (or similar) and > structured like an anonymous function, except that it doesn't accepts > arguments, but accept the

Re: [PHP-DEV] [RFC] New operator for context-dependent escaping

2016-07-22 Thread Mathieu Rochette
On 22/07/2016 16:54, Michael Vostrikov wrote: The more you compare it to a function call, the less I understand how it gains over just defining a function e() and writing I might as well just write "function e($string, $mode='html') { }" they will already have a method of doing this Ye

Re: [PHP-DEV] Pipe Operator v2

2016-07-22 Thread David Rodrigues
It's possible to use the tilde ~ easyly on keyboards? For on BR/ABNT2 is easy. So maybe use ~> as operator could be fine, instead of the triangle |>, and linear sounds good too, like: $string~>escape($$)~>dump($$); It's used currently on PHP for a bitwise operation (not), so I think that the usage

[PHP-DEV] PHP 5.5.38 is released

2016-07-22 Thread Julien Pauli
Hi. The PHP development team announces the immediate availability of PHP 5.5.38. Several security related issues were fixed in this release. All PHP 5.5 users are encouraged to upgrade to this version. Note that this should be the last PHP-5.5 release, which now reaches its end of life. All PHP 5

Re: [PHP-DEV] [RFC] New operator for context-dependent escaping

2016-07-22 Thread Michael Vostrikov
> The more you compare it to a function call, the less I understand how it gains over just defining a function e() and writing > I might as well just write "function e($string, $mode='html') { }" > they will already have a method of doing this Yes, and they have to write a call of it everywhe

Re: [PHP-DEV] [RFC] New operator for context-dependent escaping

2016-07-22 Thread Ryan Pallas
On Fri, Jul 22, 2016 at 1:31 AM, Michael Vostrikov < michael.vostri...@gmail.com> wrote: > > > The trick with the magic class name and namespace aliasing is neat, but > feels likely to confuse a lot of users > > Yes, I have to agree. Maybe more better way is to make it similar to > set_error_handl

Re: [PHP-DEV] [RFC] New operator for context-dependent escaping

2016-07-22 Thread Rowan Collins
On 22/07/2016 08:31, Michael Vostrikov wrote: sticking the escaping types after the output makes it hard to spot what's going on with anything other than a simple variable. e.g. renderView($thing->getViewName(), 'html'), 'js' ?> In Twig escapers and filters are also written after a variable, an

[PHP-DEV] NEUTRAL Benchmark Results for PHP Master 2016-07-22

2016-07-22 Thread lp_benchmark_robot
Results for project PHP master, build date 2016-07-22 06:30:29+03:00 commit: 49ddd03 previous commit:6c6567f revision date: 2016-07-21 19:03:44+02:00 environment:Haswell-EP cpu:Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz 2x18 cores, stepping 2, LLC 45 MB

Re: [PHP-DEV] Add support for arbitrary HTTP methods

2016-07-22 Thread Christoph Becker
On 22.07.2016 at 12:28, Nikita Popov wrote: > On Fri, Jul 22, 2016 at 2:28 AM, Nazar Mokrynskyi > wrote: > >> I want to bring here question about supporting custom http methods in >> built-in webserver with router script. >> >> The problem is that GET, POST are standard methods and they work fin

Re: [PHP-DEV] Add support for arbitrary HTTP methods

2016-07-22 Thread Nikita Popov
On Fri, Jul 22, 2016 at 2:28 AM, Nazar Mokrynskyi wrote: > Hi internals, > > I want to bring here question about supporting custom http methods in > built-in webserver with router script. > > The problem is that GET, POST are standard methods and they work fine, > but for custom methods like XYZ_

Re: [PHP-DEV] [RFC] New operator for context-dependent escaping

2016-07-22 Thread Michael Vostrikov
> sticking the escaping types after the output makes it hard to spot what's going on with anything other than a simple variable. e.g. renderView($thing->getViewName(), 'html'), 'js' ?> In Twig escapers and filters are also written after a variable, and this is not confusing for many users. {{ rend