Re: [PHP-DEV] [RFC] Callable constructors

2016-03-01 Thread Stanislav Malyshev
Hi! > If constructors had always been callable in PHP, this would be a > standard thing to do and not controversial imo. It's only due to > reasons lost in the mists of time, that object instantiation can only > be invoked via 'new' that it's not possible currently, and so needs an > RFC to

Re: [PHP-DEV] [RFC Proposal] var keyword deprecation/removal

2016-03-01 Thread Fleshgrinder
On 3/1/2016 6:34 PM, Rowan Collins wrote: > Rowan Collins wrote on 01/03/2016 11:33: >> >> Secondly, violating visibility may have repercussions outside actual >> errors. > > > Incidentally, PHP itself encountered this a few years ago, where a > release of libxml2 changed internal behaviour that

Re: [PHP-DEV] [RFC Proposal] var keyword deprecation/removal

2016-03-01 Thread Rowan Collins
Rowan Collins wrote on 01/03/2016 11:33: Secondly, violating visibility may have repercussions outside actual errors. Incidentally, PHP itself encountered this a few years ago, where a release of libxml2 changed internal behaviour that was being relied on for a hack. The result was that

Re: [PHP-DEV] Allowing static as a return type

2016-03-01 Thread Niklas Keller
The reason is probably that return types are currently invariant, so a inheriting class would have to declare the parent as return type anyway. Lee Davis schrieb am Di., 1. März 2016 12:46: > Hi Internals, > > whilst recently playing with return type hints on PHP 7 I

[PHP-DEV] GOOD Benchmark Results for PHP Master 2016-03-01

2016-03-01 Thread lp_benchmark_robot
Results for project PHP master, build date 2016-03-01 06:31:08+02:00 commit: 42788d6 previous commit:a1c48d5 revision date: 2016-03-01 10:51:52+08:00 environment:Haswell-EP cpu:Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz 2x18 cores, stepping 2, LLC 45 MB

[PHP-DEV] Allowing static as a return type

2016-03-01 Thread Lee Davis
Hi Internals, whilst recently playing with return type hints on PHP 7 I noticed that "static" cannot be used as a valid return type. I'm not entirely sure whether this has been purposely prevented or not. https://3v4l.org/LEXis The behaviour works it's just a parse error that's stopping it.

Re: [PHP-DEV] [RFC Proposal] var keyword deprecation/removal

2016-03-01 Thread Rowan Collins
Tony Marston wrote on 01/03/2016 09:32: "Rowan Collins" wrote in message news:56d42cd3.6020...@gmail.com... Tony Marston wrote on 29/02/2016 09:55: "James Titcumb" wrote in message news:CAKnqCEY7art1GUWG=pm0wypgqmyp0dq8oxdohgbksgq+o_b...@mail.gmail.com... Incorrect. It *may* be

Re: [PHP-DEV] [RFC Proposal] var keyword deprecation/removal

2016-03-01 Thread Jakub Kubíček
On 29 February 2016 at 15:25, Tony Marston wrote: > If "var" is automatically translated into "public", and has been since PHP 5 > emerged, and has been documented to behave in this way, then what does it > cost to leave it that way? Answer: NOTHING! Yeah. This is

Re: [PHP-DEV] [RFC Proposal] var keyword deprecation/removal

2016-03-01 Thread Tony Marston
"Rowan Collins" wrote in message news:56d42cd3.6020...@gmail.com... Tony Marston wrote on 29/02/2016 09:55: "James Titcumb" wrote in message news:CAKnqCEY7art1GUWG=pm0wypgqmyp0dq8oxdohgbksgq+o_b...@mail.gmail.com... On 28 Feb 2016 06:18, "Jakub Kubícek" wrote: I