redemption in a blog
Rails, Firefox, Anime, Mac
Gotta love those PHP error messages
In: PHP
20 Jul 2004Coding Object Oriented PHP sure has its perks, one of which is the mildly amusing error message I chanced upon below (in an implementation session that turned out to be a major debugging frenzy).
A quick search reveals the cryptic error error message to mean ‘a pair of colons’ in Hebrew. You get that when you leave in an extra ‘$’ when addressing a class method, such as:
$SomeObject::someMethod();
And no class-wide static variables in pre-version 5 PHP? Does not compute…
Categories
Archives
- July 2011
- September 2010
- June 2010
- February 2010
- January 2010
- November 2009
- September 2009
- July 2009
- June 2009
- March 2009
- November 2008
- September 2008
- August 2008
- June 2008
- May 2008
- April 2008
- March 2008
- February 2008
- January 2008
- December 2007
- November 2007
- October 2007
- September 2007
- August 2007
- July 2007
- June 2007
- May 2007
- April 2007
- March 2007
- February 2007
- January 2007
- December 2006
- November 2006
- October 2006
- September 2006
- August 2006
- July 2006
- April 2006
- March 2006
- February 2006
- January 2006
- December 2005
- July 2005
- April 2005
- March 2005
- February 2005
- January 2005
- December 2004
- November 2004
- October 2004
- September 2004
- August 2004
- July 2004
- June 2004
- May 2004
- April 2004
- March 2004
- February 2004
- January 2004
- December 2003
- November 2003
- October 2003
- September 2003
- August 2003
- July 2003
- June 2003
- May 2003
14 Responses to Gotta love those PHP error messages
Stephan Segraves
July 21st, 2004 at 2am
I know what you mean about it feeling like it’s broken… After spending a ton of time using Java and being so strict with the way I handle objects, pass values, and implement I am somewhat reluctant to give it a go in PHP.
TeRanEX
July 21st, 2004 at 2am
There is a PHP parser that highlights syntax errors available as a plugin for jEdit (a lovely editor!), but I haven’t tried it myself yet because it needs the current development version of jEdit (4.2) and i’m using the stable version (4.1)
You can find jEdit here: http://www.jedit.org/
and the plugin here: http://plugins.jedit.org/plugins/?PHPParser
Oh, if you want to see a screenshot of jEdit: http://budts.be/weblog/item/332 (last 2 shots)
jsurfer
July 21st, 2004 at 11pm
The PHPeclipse Eclipse plugin contains an internal PHP parser, which should show much PHP parse errors.
But it’s not perfect at the moment.
sidu
August 11th, 2004 at 11pm
Just testing please dont mind it…. :)
sidu
August 11th, 2004 at 11pm
Just testing please dont mind it…. :)
TeRanEX
August 13th, 2004 at 10am
Just to let you know:
I installed jEdit 4.2 and the PHP Parser Plugin and it really works nice. Every time you open or save a php file it is being parsed and all errors are nicely shown in an errorlist.
Cheah Chu Yeow
July 21st, 2004 at 1am
Dan: Well, that’s one of the main premises of an interpreted language I guess. Though what you said about a syntax checker would be cool.
Aaron: Nah it’s not fun. It feels semi-broken (but mind you, I come from a Java programming background).
Khlo: Yup it means ‘a pair of colons’ in Hebrew.
Khlo
July 21st, 2004 at 1am
paamayim nekudotayim seems to be the official name of the :: notation – look at the manual:
http://uk2.php.net/manual/en/keyword.paamayim-nekudotayim.php
Wonder if it means something in some foreign language.
Aaron Brazell
July 21st, 2004 at 1am
I really need to foray into OOP PHP. I am missing so much fun. :p
Dan Allen
July 20th, 2004 at 11pm
I have done a lot of programming in PHP and I concur, that parse errors are often times very bizarre. The runtime errors which PHP generates are very informative, especially with the backtrace function in PHP 4.2.
One nice aspect of Java is that you know when you execute the program that all parse errors are gone. I wonder if there is a syntax checker written for the PHP language that would assist in checking your code for validatity. It wouldn’t be a bad idea. Then you could setup ant to run it on your project.
Meitar
October 7th, 2004 at 10pm
:) I’ve never seen that error myself, but it’s not at all cryptic for me: I speak Hebrew.
Coca IQ Bogdan
January 5th, 2005 at 1pm
Yes, and something much more funny about this error, did anybody tried to set : error_reporting(0);
Because if you will do it so … you will still see the error!!! WOW!
Cheah Chu Yeow
January 5th, 2005 at 8pm
Um, I think that is because it is a fatal parse error. To stop displaying all errors, set the display_errors configuration setting in your php.ini to ‘off’ instead.
Jeff
August 2nd, 2005 at 2pm
$php -l myfile.php
Will do a parser check on your file.