php > The difference between whether to close the tag or not: 1. If you close the tag, it will cause redundant output, php errors or blank pages, etc.; 2. If you do not close the tag, you can prevent harmful content after closing the tag; 3. If it is mixed use, you still need to write a closing tag.
#The operating environment of this article: Windows7 system, PHP7.1, Dell G3.
php >What are the differences between yes and no? What are the benefits of not writing closing tags in PHP?
When I first started writing PHP code, I wanted to write PHP closing tags. In the past few years, my habit has changed and I no longer write PHP tags.
I first came into contact with this concept from Drupal. I was a little uncomfortable at first - why not write a closing tag? This feels very imperfect, and very uncomfortable for people with obsessive-compulsive disorder! Later, I encountered problems caused by closing tags at work, so I started not writing closed tags.
After reading some articles, the summary of PHP closing tags is as follows:
Benefits:
If this is a program included by others, without this terminator, it can be reduced There are many problems, such as: header, setcookie, session_start, these actions cannot have output before. If you accidentally add invisible characters (extra spaces, newlines) after ?> to damage the page display, "Header" will be reported. already sent" error. If you don't write it, you won't have this problem. In addition, you can directly move the cursor to the end and continue programming.
Disadvantages:
In dreamweaver's view mode, it's a mess.
The official explanation about the PHP closing tag is: The PHP closing tag "?>" is optional for the PHP analyzer in PHP. However, if a closing tag is used, any space inserted after the closing tag by a developer, user, or FTP application may cause redundant output, PHP errors, subsequent output that cannot be displayed, and a blank page. Therefore, all PHP files should omit the PHP closing tag and insert a comment to indicate that this is the bottom of the file and locate the file relative to the application. This will help you make sure that the file has ended and not been deleted.
This is also mentioned in Zend’s code specification: http://framework.zend.com/manual/1.12/en/coding-standard.php-file-formatting.html
Code example:
Inappropriate:
The code is as follows:
<?php echo "Here's my code!"; ?>
Appropriate:
The code is as follows:
<?php echo "Here's my code!"; /* End of file myfile.php */ /* Location: ./system/modules/mymodule/myfile.php */
Therefore , if it is a pure PHP code file, the ?> end identifier should be omitted.
Recommended learning: "PHP Video Tutorial"
The above is the detailed content of php>The difference between whether or not. For more information, please follow other related articles on the PHP Chinese website!

The article compares ACID and BASE database models, detailing their characteristics and appropriate use cases. ACID prioritizes data integrity and consistency, suitable for financial and e-commerce applications, while BASE focuses on availability and

The article discusses securing PHP file uploads to prevent vulnerabilities like code injection. It focuses on file type validation, secure storage, and error handling to enhance application security.

Article discusses best practices for PHP input validation to enhance security, focusing on techniques like using built-in functions, whitelist approach, and server-side validation.

The article discusses strategies for implementing API rate limiting in PHP, including algorithms like Token Bucket and Leaky Bucket, and using libraries like symfony/rate-limiter. It also covers monitoring, dynamically adjusting rate limits, and hand

The article discusses the benefits of using password_hash and password_verify in PHP for securing passwords. The main argument is that these functions enhance password protection through automatic salt generation, strong hashing algorithms, and secur

The article discusses OWASP Top 10 vulnerabilities in PHP and mitigation strategies. Key issues include injection, broken authentication, and XSS, with recommended tools for monitoring and securing PHP applications.

The article discusses strategies to prevent XSS attacks in PHP, focusing on input sanitization, output encoding, and using security-enhancing libraries and frameworks.

The article discusses the use of interfaces and abstract classes in PHP, focusing on when to use each. Interfaces define a contract without implementation, suitable for unrelated classes and multiple inheritance. Abstract classes provide common funct


Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

SublimeText3 Linux new version
SublimeText3 Linux latest version

Dreamweaver Mac version
Visual web development tools

ZendStudio 13.5.1 Mac
Powerful PHP integrated development environment

SecLists
SecLists is the ultimate security tester's companion. It is a collection of various types of lists that are frequently used during security assessments, all in one place. SecLists helps make security testing more efficient and productive by conveniently providing all the lists a security tester might need. List types include usernames, passwords, URLs, fuzzing payloads, sensitive data patterns, web shells, and more. The tester can simply pull this repository onto a new test machine and he will have access to every type of list he needs.

SublimeText3 Mac version
God-level code editing software (SublimeText3)