'echo' or drop out of 'programming' write HTML then start PHP code again

For the most part, when I want to display some HTML code to be actually rendered I would use a 'close PHP' tag, write the HTML, then open the PHP again. eg

<?php
// some php code
?>
<p>HTML that I want displayed</p>
<?php
// more php code
?>

But I have seen lots of people who would just use echo instead, so they would have done the above something like

<?php
// some php code
echo("<p>HTML that I want displayed&l开发者_StackOverflow社区t;/p>");
// more php code
?>

Is their any performance hit for dropping out and back in like that? I would assume not as the PHP engine would have to process the entire file either way.

What about when you use the echo function in the way that dose not look like a function, eg

echo "<p>HTML that I want displayed</p>"

I would hope that this is purely a matter of taste, but I would like to know if I was missing out on something. I personally find the first way preferable (dropping out of PHP then back in) as it helps draw a clear distinction between PHP and HTML and also lets you make use of code highlighting and hinting for your HTML, which is always handy.

The first type is preferable, exactly for the reasons you mentioned.

Actually, echoing out whole chunks of html is considered bad practice.

No, there's no performance increase that would be visible.

Sometimes its just simply easier to output content using echo (for example, when inside a while or for loop) than to close the php tag.

I think there's a preprocessor which converts the same form into the second. That's what happens in ASP.NET, anyway. And in both ASP.NET and classic ASP, loops can actually stretch across raw-HTML regions.

There's no performance difference at all.

Just the style that produces the most readable code. Depending on the actual situation that can be either of the two.

But mixing HTML and PHP should be avoided where possible anyway. THis can be accomplished by using a template system for your views.