PHP Closing Tags Considered Harmful

Of course, if you're embedding HTML in PHP, or vice versa, you'll need to use closing tags to demarcate the two languages. But given a file containing only PHP code, the closing tag is completely superfluous.

Worse, the closing tag is potentially harmful, since any whitespace, accidental or otherwise, after the tag will be sent to the browser as output, with potentially catastrophic effects:

• Any output, even that tiny bit of whitespace, being sent to the browser will cause PHP to send the HTTP response headers. This means that if, later on in your script, you wish to specify an HTTP header - such as a redirect - or drop a cookie, this will fail. Instead you'll generate the "Cannot modify header information - headers already sent" warning message, with which every PHP developer will be more than familiar
• If your output is in a fragile binary format, such as an image or SWF file, spurious whitespace has the potential to corrupt the file
• If you're outputting markup, leading newlines will push your XML prolog or Doctype Declaration off the top line of the output, thus rendering your markup invalid. I've had first-hand experience of this issue preventing sites from displaying at all on some mobile devices, which tend to be a bit more temperamental than full Web browsers when it comes to parsing markup

In any of these cases, tracking down an errant fragment of whitespace in a large codebase will be more pain than you really want. That's why omitting the closing tag is part of the Zend Framework coding standards among others.

So there you go. The solution is simple: stop using PHP closing tags.