Differences Between Two Printing Commands In PHP
July 19, 2008
PHP is a highly robust language- one that has attracted web developers from all across the world to take place in the web application craze that’s been raging. Getting the most out of the language means understanding it- and something most developers don’t know is simple things such as the difference between Echo and Print.
Everyone in the PHP web development community is familiar with Echo and Print- two commands to output data to the screen. But what they may not know is that the two have the same output and similar structure- so why two commands for the same task?
As it turns out, Echo is actually a language construct that doesn’t return a value, in which Print does. This simple fact means that Print can be used in some instances where Echo can’t, although developers will probably never run into such a situation. In fact, many PHP developers stick with Echo their entire career and will never see a problem.
There is the issue of speed that comes along with the fact that Print has to return a value. The extra load will indeed affect performance, but on such a small level that it isn’t even noticeable. It is recommended that PHP developers not take such a trivial amount of performance into mind, and instead pick the printing command that best suits them.
So far the industry standard has been to use Echo, but it should be stressed that either command may be used at will. Echo seems to be the favorite as it is easier to type, not to mention it’s a fun word to say! Those who favor the Print command are usually older programmers, who are accustomed to using the command Print from other programming languages that are now considered archaic.
Even though speed should always be an issue, it’s important to focus one’s attention not on selecting a language construct for printing- but rather how they use it. Too often developers will use multiple Print or Echo calls, only to organize their code. But this can drastically degrade performance if enough calls are made, so it’s recommended to choose the language construct of one’s choice- but use it wisely.
In Conclusion
PHP development just wouldn’t be the same without fun debates such as the one just mentioned. But in reality, it really doesn’t matter which route is taken- so long as either language construct is used in a performance-based manner. Although Print may still have somewhat of a following today, as books and publishers start using Echo more often, it’s likely we’ll see a death to the Print command soon enough.
Comments
Got something to say?