Why do some scripts omit the closing PHP tag, '?>'? [duplicate]

This question already has answers here: Why would one omit the close tag? (14 answers) Closed 8 years ago.

In some scripts I see that they omit writing a closing tag ?> for the script. Why is it and should I do this as we开发者_如何学Cll?

(I'm sure they have not forgotten it.)

---

Well, omitting the closing tag is just one solution for avoiding blanks and other characters at the end of file. For example any char which is accidentally added behind the closing tag would trigger an error when trying to modify header info later.

Removing the closing tag is kind of "good practice" referring to many coding guidelines.

---

From PHP: Instruction Separation

The closing tag of a PHP block at the end of a file is optional, and in some cases omitting it is helpful when using include() or require(), so unwanted whitespace will not occur at the end of files, and you will still be able to add headers to the response later. It is also handy if you use output buffering, and would not like to see added unwanted whitespace at the end of the parts generated by the included files.

---

php.net on PHP tags:

If a file is pure PHP code, it is preferable to omit the PHP closing tag at the end of the file. This prevents accidental whitespace or new lines being added after the PHP closing tag, which may cause unwanted effects because PHP will start output buffering when there is no intention from the programmer to send any output at that point in the script.

---

They do it to avoid risking to have whitespaces after the closing tag which may stop headers to work.

This is, of course, true for PHP-only files.

---

CodeIgniter Framework suggests to omit closing tags for

"... can cause unwanted output, PHP errors or blank pages".

You can read it here.

---

Modern versions of PHP set the output_buffering flag in php.ini. If output buffering is enabled, you can set HTTP headers and cookies after outputting HTML, because the returned code is not sent to the browser immediately.

Are the examples still valid in this context?

---

1. It shows unwanted white space / blank page. HTTP headers do not work for those unwanted whitespace.
2. Most JavaScript injection is made at the end of the file. It will show an error message and breaks the code, injected JavaScript code does not get executed.