On 9 March 2015 at 11:04, David Zuelke d...@heroku.com wrote:
Why not wait with the merge until a consensus emerges regarding Throwable?
The patch for engine exceptions is large - the longer that it is left
unmerged, the more difficult it will be to do and people's time is
valuable. It also
Am 09.03.2015 um 12:04 schrieb David Zuelke d...@heroku.com:
Why not wait with the merge until a consensus emerges regarding Throwable?
On 09.03.2015, at 05:26, Nikita Popov nikita@gmail.com wrote:
On Mon, Feb 23, 2015 at 7:15 PM, Nikita Popov nikita@gmail.com wrote:
Hi
There's a cultural disposition against re-purposing a symbol from one major
version to the next. Let's consider that as fact and move on.
If I wanted to provide syntactic sugar to replace a symbol with $this- so
that our code can become more expressive if we choose to use it, how would
you
Hi Shawn,
My opinion is that even though the @ operator should be deprecated in
further along the line removed, it should not be repurposed for anything,
it has too much legacy imho.
While a shortcut might be a good idea, I personally favour the $this-var
syntax just for muscle memory if nothing
I guess that if I thought that PHP would change its scoping, I would have
tried for that.
On Mon, Mar 9, 2015 at 3:11 PM, Mike Dugan m...@dugan.io wrote:
Why not use regular variable naming ($foo) and check the object for
accessible instance vars before looking for locally scoped vars? I’ve no
Am 09.03.2015 um 12:40 schrieb Dan Ackroyd:
So even though I hope we can clean up the exception hierarchy, merging
the engine exceptions is the right choice imo.
Sounds reasonable to me. I'm wondering, though, whether we really need
an additional RFC for the change I suggested as nobody spoke
On Mar 8, 2015 9:26 PM, Nikita Popov nikita@gmail.com wrote:
On Mon, Feb 23, 2015 at 7:15 PM, Nikita Popov nikita@gmail.com
wrote:
Hi internals!
Voting on the engine exceptions RFC, which proposes to convert existing
fatal and recoverable fatal errors into exceptions, has opened:
On Mar 9, 2015 1:24 PM, Derick Rethans der...@php.net wrote:
On Fri, 27 Feb 2015, Xinchen Hui wrote:
Hey Internals:
I was looking Bob's switch optimization..
then I start to worry about where is the place optimization
should goes..
in generally, PHP is a
Am 09.03.2015 um 11:24 schrieb Derick Rethans der...@php.net:
On Fri, 27 Feb 2015, Xinchen Hui wrote:
Hey Internals:
I was looking Bob's switch optimization..
then I start to worry about where is the place optimization should
goes..
in generally, PHP is a
On Mon, Mar 9, 2015 at 3:52 PM, Bob Weinand bobw...@hotmail.com wrote:
Am 09.03.2015 um 11:24 schrieb Derick Rethans der...@php.net:
On Fri, 27 Feb 2015, Xinchen Hui wrote:
Hey Internals:
I was looking Bob's switch optimization..
then I start to worry about where is
Sure, they should be separated into two equally impossible to pass RFCs.
However, do you see a reasonable alternative way to achieve this type of
improvement?
On Mon, Mar 9, 2015 at 2:48 PM, Mike Dugan m...@dugan.io wrote:
Shawn Stellan,
(Apologies if this gets delivered twice, had to
Hi, I’d like to start vote on RFC:continue_ob — any objections?
https://wiki.php.net/rfc/continue_ob https://wiki.php.net/rfc/continue_ob
Regards,
Mike
On Mon, Mar 9, 2015 at 5:35 AM, Derick Rethans der...@php.net wrote:
On Thu, 5 Mar 2015, Trevor Suarez wrote:
Good morning internals!
I would like to propose a small addition be made to the DateTime class.
https://github.com/php/php-src/pull/1145
When the factory method was added, we had
Hi
2015-03-09 15:11 GMT+01:00 Shawn McCool sh...@heybigname.com:
I guess that if I thought that PHP would change its scoping, I would have
tried for that.
Well take this code into consideration:
?php
class A {
protected $b;
function c($b) {
$b = $b; // does not work
}
On top of the cultural disposition, there is also the fact that things
should not be removed from the language without deprecating them, so at
best 7.0 would emit and E_DEPRECATED for the usage of @.
- Stelian
On Mon, Mar 9, 2015 at 3:31 PM, Kalle Sommer Nielsen ka...@php.net wrote:
Hi
Hi,
I think your idea is good.
Le Mon, 09 Mar 2015 15:11:01 +0100, Shawn McCool sh...@heybigname.com a
écrit:
There's a cultural disposition against re-purposing a symbol from one
major
version to the next. Let's consider that as fact and move on.
If I wanted to provide syntactic sugar
Hi, internals!
The Generator Delegation RFC has been updated significantly and marked as
v0.2.0:
https://wiki.php.net/rfc/generator-delegation
There now exists a final patch and the proposed syntax has been changed
from
yield * expr
to
yield from expr
I encourage all interested
Hi, internals!
I'd like to announce voting for the Generator Return Expressions RFC:
https://wiki.php.net/rfc/generator-return-expressions#vote
As this is a fairly concise and straightforward proposal the voting period
will last only one week. A two-thirds majority is required for acceptance.
Hi,
This is a remainder that the voting for the Strict Argument Count RFC is
scheduled to start on March 14th, so we still have this week for discussion
and it's still a good time to give feedback.
Thanks,
Márcio
2015-03-01 20:02 GMT-03:00 Marcio Almada marcio.w...@gmail.com:
Hi, internals
On 9 March 2015 09:43:32 GMT, Shawn McCool sh...@heybigname.com wrote:
In order to access instance variables, one must use the `$this-`
prefix.
The problem with this is that it reduces expressiveness in the language
and
increases the amount of unnecessary decoration, reducing readability.
I
Hey
as developing both Java and PHP, I would suggest a solution similar to
Java. As long as there is no conflict to a local variable the keyword
$this should be the default.
Regards
DerOetzi
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit:
Hi!
The problem with this is that it reduces expressiveness in the
language and increases the amount of unnecessary decoration,
reducing readability.
I disagree with this premise. The $this here is not just decorative
syntax, it's an actual variable, which can be passed around just like
Mike Dugan just told me § and £ aren't standard symbols, and he is right, I
didn't have a picture of a standard keyboard when I proposed these symbols
:(
I don't know what could be used instead. Certainly a combination of symbols,
but I can't find one.
Someone got an idea ?
Regards.
Benoit
Matthew,
On Sun, Mar 8, 2015 at 11:04 PM, Matthew Leverton lever...@gmail.com wrote:
$foo = class extends Callback { ... }
$bar = new $foo;
Nope, none of that. Wrap that in a function or clone it perhaps.
Are you actively against that functionality? (I don't think it's very
useful, but was
Someone got an idea ?
Simply arrows, without word this
?php
class Addition {
private $number
public function __construct($number) {
$-number = $number;
}
public function original() {
return $-number;
}
public function addTo($amount) {
return $-number + $amount;
}
}
Hi!
as developing both Java and PHP, I would suggest a solution similar to
Java. As long as there is no conflict to a local variable the keyword
$this should be the default.
As long as there is a key. There may be conflict, and unlike Java
PHP's properties are dynamic. Java way is very hard
On Thu, 5 Mar 2015, Trevor Suarez wrote:
Good morning internals!
I would like to propose a small addition be made to the DateTime class.
https://github.com/php/php-src/pull/1145
When the factory method was added, we had this same discussion. And the
discussions lead to the conclusion
I've never submitted an RFC. Whether or not you're interested in the
feature, please consider giving me feedback on the RFC itself so that I can
better understand how to succeed in the process.
== PHP RFC: Instance Variable Sugar ==
* Version: 0.1
* Date: 2015-03-09
* Author: Shawn
Hey Shane,
The @ symbol in PHP is currently an error control operator[1]. Does that
mean you will be reassigning the error control operator to another
character?
[1]: http://php.net/manual/en/language.operators.errorcontrol.php
On Monday, March 9, 2015, Shawn McCool sh...@heybigname.com wrote:
Hi,
On 9 March 2015 at 17:43, Shawn McCool sh...@heybigname.com wrote:
I've never submitted an RFC. Whether or not you're interested in the
feature, please consider giving me feedback on the RFC itself so that I can
better understand how to succeed in the process.
== PHP RFC: Instance
Why not wait with the merge until a consensus emerges regarding Throwable?
On 09.03.2015, at 05:26, Nikita Popov nikita@gmail.com wrote:
On Mon, Feb 23, 2015 at 7:15 PM, Nikita Popov nikita@gmail.com wrote:
Hi internals!
Voting on the engine exceptions RFC, which proposes to
Hi Gregory,
On Sun, Mar 8, 2015 at 7:03 PM, Grégory Planchat greg...@luni.fr wrote:
Le 08/03/2015 00:44, Yasuo Ohgaki a écrit :
Hi Gregory,
On Sun, Mar 8, 2015 at 2:12 AM, Grégory Planchat greg...@luni.fr wrote:
Le 07/03/2015 02:39, Yasuo Ohgaki a écrit :
We may provide new names and
Hi Rowan,
On Mon, Mar 9, 2015 at 7:42 AM, Rowan Collins rowan.coll...@gmail.com
wrote:
On 08/03/2015 01:15, Yasuo Ohgaki wrote:
On Sun, Mar 8, 2015 at 3:39 AM, Rowan Collins rowan.coll...@gmail.com
mailto:rowan.coll...@gmail.com wrote:
To an extent, yes. Part of the point that I and
On Tue, Mar 10, 2015 at 1:48 PM, Xinchen Hui larue...@php.net wrote:
Hey:
On Tue, Mar 10, 2015 at 10:07 AM, Yasuo Ohgaki yohg...@ohgaki.net wrote:
Hi Reeze,
On Mon, Mar 9, 2015 at 12:56 PM, reeze re...@php.net wrote:
It is a deprecated warning I won't break code I think.
This could makes
On 03/09/2015 04:26 PM, Rowan Collins wrote:
On 9 March 2015 09:43:32 GMT, Shawn McCool sh...@heybigname.com wrote:
In order to access instance variables, one must use the `$this-`
prefix.
The problem with this is that it reduces expressiveness in the language
and
increases the amount of
Hi Reeze,
On Mon, Mar 9, 2015 at 12:56 PM, reeze re...@php.net wrote:
It is a deprecated warning I won't break code I think.
This could makes those project more maintainable (new PHP programmer could
be easier to maintain the code without surprise), and it will be trivial to
fix this. We
Hey:
On Tue, Mar 10, 2015 at 10:07 AM, Yasuo Ohgaki yohg...@ohgaki.net wrote:
Hi Reeze,
On Mon, Mar 9, 2015 at 12:56 PM, reeze re...@php.net wrote:
It is a deprecated warning I won't break code I think.
This could makes those project more maintainable (new PHP programmer could
be easier
Hi Mike,
On Mon, Mar 9, 2015 at 9:45 PM, Michael Wallner m...@php.net wrote:
Hi, I’d like to start vote on RFC:continue_ob — any objections?
https://wiki.php.net/rfc/continue_ob https://wiki.php.net/rfc/continue_ob
+1
I don't mind at all even if you fix this as simple bug fix :)
Regards,
Hi Pierre and all,
On Tue, Mar 10, 2015 at 11:59 AM, Pierre Joye pierre@gmail.com wrote:
On Tue, Mar 10, 2015 at 1:48 PM, Xinchen Hui larue...@php.net wrote:
Hey:
On Tue, Mar 10, 2015 at 10:07 AM, Yasuo Ohgaki yohg...@ohgaki.net
wrote:
Hi Reeze,
On Mon, Mar 9, 2015 at 12:56 PM,
Hi Marcio,
Just passing by to announce I already have a working version of the new
patch: https://github.com/php/php-src/pull/1158
The patch is 100% compatible with the proposed one with the advantages:
- Has no regression or forward compatibility risks and is highly
predictable
-
Am 09.03.2015 um 09:44 schrieb Matteo Beccati:
I like the approach. I'm no lexer expert but the new PR seems much nicer.
Moreover, I like the feature itself but previously voted no on the
implementation. I've therefore switched my vote to a yes.
Dito.
--
PHP Internals - PHP Runtime
On Fri, 27 Feb 2015, Xinchen Hui wrote:
Hey Internals:
I was looking Bob's switch optimization..
then I start to worry about where is the place optimization should
goes..
in generally, PHP is a interpreted language. IMO, it should
compiler the PHP codes to opcode
42 matches
Mail list logo
