in Best Practices, Web Architecture

Is This Ever OK?

As a developer I’m often torn between the concept of “it works” and the concept of “it’s right.” This is no less true than in the following example…


class Foo

     public $property;

     public function outputProperty($var = null)

          // Some function processing here.

          The value of the property is <?php echo $this->property; ?>
          <!-- html here !-->





There’s great debate amongst the PHP community about when exiting PHP and printing strict HTML is permissible; this example clearly works (you can test it), but is it right?

In terms of readability, it’s terrible. If you’re in the midst of a class and all of a sudden you’re outputting straight HTML, it can confuse a reader. The best commenting in the world can’t help. Most programs that do code highlighting highlight PHP and echo() statements differently.

But on the other side, if you’re going to do a big long string of PHP, and you want to throw in some javascript, doing this isn’t very practical, especially if you have lots of Javascript and, like me, place your strings in single quotes rather than double quotes.

So what do you think, PHP community? Give me your thoughts.

Frustrated with your company’s development practices?

You don't have to be!

No matter what the issues are, they can be fixed. You can begin to shed light on these issues with my handy checklist.

Plus, I'll help you with strategies to approach the issues at the organization level and "punch above your weight."

Powered by ConvertKit
Brandon Savage is the author of Mastering Object Oriented PHP and Practical Design Patterns in PHP
  1. While I wouldn’t consider myself someone in a position to tell most people reading this what to do, I think I would pummel my devs if they did this. Partly for readability, partly because it seems off, but mostly because I can be pretty certain that layout and presentation is going to be making its way into your business logic.

    One quick solution is to just pull the html out into a new php file and turn it into an include or require. Though even that case you would want to take a serious look at the overall architecture of your site as again you probably have a class trying to do too much.

Comments are closed.