Court Ewing has a new post to his blog describing some of the most common cryptic errors that you might come across in your day-to-day development.
If you've been programming for awhile, then you've probably experienced your fair share of cryptic error messages. It's understandable that building in detailed error messages that are clear to even novice developers is not always a high priority for programming languages when there are so many other features to create and issues to address. The PHP language has decent error messages, but it is by no means an exception to this rule.
The three errors he covers are probably familiar to anyone that's been working with PHP for any length of time:
- Fatal error: Parse error: syntax error, unexpected T_PAAMAYIM_NEKUDOTAYIM
- Fatal error: Can't use function return value in write context
- Fatal error: Exception thrown without a stack frame in Unknown on line 0