It's amazing to me this has become such a long discussion. The facts are
simple:
1) People don't ask for the other parse errors even half as often as they as
for T_PAAMAYIM_NEKUDOTAYIM
2) They do so because it looks like gibberish to them, so it looks unlikely
to be a common thing you can
-Oorspronkelijk bericht-
Van: Stan Vass [mailto:sv_for...@fmethod.com]
Verzonden: maandag 1 november 2010 10:19
Aan: internals@lists.php.net
Onderwerp: [SPAM] Re: [PHP-DEV] rename T_PAAMAYIM_NEKUDOTAYIM to
T_DOUBLE_COLON
Urgentie: Laag
It's amazing to me this has become such a
Agreed, and really - my experience is that googling non-standard error
message usually give instant result. Googling for a common error
message could become a big time investment pointing to different
software even if you point to search engine for what software to look.
2010/11/1 Dennis
On 30 October 2010 01:47, admin ad...@codeangel.org wrote:
WTF is T_PAAMAYIM_NEKUDOTAYIM?
This has to be THE most asked question by new php developers when they come
across it. Can we please change the token name to T_DOUBLE_COLON so I don't
have to hear about it constantly?
Those that
On Mon, Nov 01, 2010 at 10:58:36AM +0100, Dennis Haarbrink wrote:
Come on people, what exactly is the problem with a once-in-a-lifetime
investment of 5 seconds of your time to google some stupid error message.
Something you, as a developer, spend your life doing.
Please, stop complaining
On 01 Nov 2010, at 12:06, Alexander Schrijver wrote:
Its a minor change and an annoyance to a lot of people. Yes, by not changing
this you'r annoying thousands of people.
Instead of going for this cosmetic nonsense you should help those people on the
lemon branch.
I am insulted every time I
+1
This solves lots of other problems we have and will have in the future.
--
James Butler
Sent from my iPhone
On 1 Nov 2010, at 12:00, Stefan Marr p...@stefan-marr.de wrote:
On 01 Nov 2010, at 12:06, Alexander Schrijver wrote:
Its a minor change and an annoyance to a lot of people. Yes,
On Mon, Nov 01, 2010 at 12:59:54PM +0100, Stefan Marr wrote:
On 01 Nov 2010, at 12:06, Alexander Schrijver wrote:
Its a minor change and an annoyance to a lot of people. Yes, by not changing
this you'r annoying thousands of people.
Instead of going for this cosmetic nonsense you should
-Original Message-
From: Alexander Schrijver [mailto:alexander.schrij...@gmail.com]
Sent: 01 November 2010 12:19
To: Stefan Marr
Cc: Dennis Haarbrink; Stan Vass; internals@lists.php.net
Subject: Re: [PHP-DEV] RE: [SPAM] Re: [PHP-DEV] rename T_PAAMAYIM_NEKUDOTAYIM
to T_DOUBLE_COLON
On
Oops, should've sent this to the list too.
- Forwarded message from Alexander Schrijver
alexander.schrij...@gmail.com -
Date: Mon, 1 Nov 2010 13:28:59 +0100
From: Alexander Schrijver alexander.schrij...@gmail.com
To: James Butler james.but...@edigitalresearch.com
Subject: Re: [PHP-DEV]
On Nov 01 13:30:58, Alexander Schrijver wrote:
Oops, should've sent this to the list too.
- Forwarded message from Alexander Schrijver
alexander.schrij...@gmail.com -
Date: Mon, 1 Nov 2010 13:28:59 +0100
From: Alexander Schrijver alexander.schrij...@gmail.com
To: James Butler
On Mon, Nov 01, 2010 at 01:36:24PM +0100, Etienne Kneuss wrote:
It's the policy:
There are two reasons this term will stay. It is a tip of the hat to
the amount of PHP work that came out of Israel, and it is a good
reminder that
On Mon, Nov 1, 2010 at 1:23 PM, James Butler
james.but...@edigitalresearch.com wrote:
-Original Message-
From: Alexander Schrijver [mailto:alexander.schrij...@gmail.com]
Sent: 01 November 2010 12:19
To: Stefan Marr
Cc: Dennis Haarbrink; Stan Vass; internals@lists.php.net
Subject:
On Mon, Nov 1, 2010 at 1:43 PM, Alexander Schrijver
alexander.schrij...@gmail.com wrote:
On Mon, Nov 01, 2010 at 01:36:24PM +0100, Etienne Kneuss wrote:
It's the policy:
There are two reasons this term will stay. It is a tip of the hat to
the amount of PHP work that came out of
On Nov 01 13:43:14, Alexander Schrijver wrote:
On Mon, Nov 01, 2010 at 01:36:24PM +0100, Etienne Kneuss wrote:
It's the policy:
There are two reasons this term will stay. It is a tip of the hat to
the amount of PHP work that came out of Israel, and it is a good
Stan Vass wrote:
It's amazing to me this has become such a long discussion. The facts are
simple:
1) People don't ask for the other parse errors even half as often as
they as for T_PAAMAYIM_NEKUDOTAYIM
2) They do so because it looks like gibberish to them, so it looks
unlikely to be a common
On Mon, Nov 1, 2010 at 2:10 PM, Nathan Rixham nrix...@gmail.com wrote:
Makes sense, just alias it and change the error message thus keeping bc.
Please just move on.
Everything possible has been said already. If we feel like there are
critical issues introduced by this error message, then we
Can we get some opinions on this. I'm willing to make the changes, but I
want to get some sort of consensus on this.
Basically I believe the problem is that patch 42838 should be reverted and
the documentation should be updated. Someone on IRC had disagreed with me
so I want more opinions
Hi,
2010/11/1 Lonny K lon...@gmail.com
Can we get some opinions on this. I'm willing to make the changes, but I
want to get some sort of consensus on this.
Basically I believe the problem is that patch 42838 should be reverted and
the documentation should be updated. Someone on IRC had
On Fri, October 29, 2010 7:47 pm, admin wrote:
WTF is T_PAAMAYIM_NEKUDOTAYIM?
This has to be THE most asked question by new php developers when they
come across it. Can we please change the token name to T_DOUBLE_COLON
so I don't have to hear about it constantly?
Those that disagree don't
2010/11/1 Richard Lynch c...@l-i-e.com
On Fri, October 29, 2010 7:47 pm, admin wrote:
WTF is T_PAAMAYIM_NEKUDOTAYIM?
This has to be THE most asked question by new php developers when they
come across it. Can we please change the token name to T_DOUBLE_COLON
so I don't have to hear
On 11/1/10 1:47 PM, Felipe Pena wrote:
2010/11/1 Richard Lynch c...@l-i-e.com
On Fri, October 29, 2010 7:47 pm, admin wrote:
WTF is T_PAAMAYIM_NEKUDOTAYIM?
This has to be THE most asked question by new php developers when they
come across it. Can we please change the token name to
Hi,
we're a bit further along now; and with the typehinting resolved
(http://thread.gmane.org/gmane.comp.php.devel/62298/focus=62858) I want
to start started with PHP 5.4 with the first alpha on Wednesday,
November 24th. There are a few things that need sorting
out and/or clarification:
-
Hi!
The RFC on annotations for PHP http://wiki.php.net/rfc/annotations
suggests to add new syntax to the language to provide meta data for use
in reflection. This sort of meta data is usually provided in the form of
docblocks, which this RFC does *not* state isn't good enough.
The discussion
On Nov 01 15:33:59, Derick Rethans wrote:
Hi!
Work has been done on rewriting the PHP parser to Lemon in a specific
branch: http://svn.php.net/viewvc/php/php-src/branches/LEMON/
Right now, the Lemon parser is not actually faster than the current
bison parser, so I would suggest not to
On Mon, 1 Nov 2010, Derick Rethans wrote:
I understand that the general idea is to bundle APC with a future
version of PHP. Right now, APC doesn't really compile for trunk because
of internal changes. However, for PHP 5.3 it's getting into a pretty
good shape. In order to add APC, what
Hi,
2010/10/19 Derick Rethans der...@php.net
Hi!
On Sun, 5 Sep 2010, Derick Rethans wrote:
I've spend some more time on this, and have attached a new patch that:
- Removes the strict type verification, changing it back into typehints
only.
- Keeps the current syntax so that
Hi!
(http://thread.gmane.org/gmane.comp.php.devel/62298/focus=62858) I want
to start started with PHP 5.4 with the first alpha on Wednesday,
November 24th. There are a few things that need sorting
I just wanted to remind we have ZendCon this week, which means some
people who might have
Hi Derick,
I'm all for it.
Although I have karma, I'm not an active PHP core contributor, but I
would like to participate of such discussion, mainly because I have
plenty experience with Annotations from another languages.
I'll spend some time re-reading the entire Annotations thread and come
up
29 matches
Mail list logo