<?php
   
  foreach(array('emp', 'mgr') as $prefix) {
      $data[($prefix == 'emp') ? 'employee' : 'manager'] = 1;
  }
  
  print_r($data);
?>

Array
(
    [employee] => 1
    [manager] => 1
)

aisa0

1. HTML should pass validation by The W3C Markup Validation Service. My personal preference is for XHTML 1.0 Strict, or XHTML 1.1, but I can't honestly say that I have any reason for preferring them over HTML 4.01. Whatever is used, though, it should validate against the standard, because the standard is what browser authors use, or at least ought to be using, to write their parsing and rendering engines, and I believe that if one sticks to the standard, one runs the least risk of the newest revision of some browser breaking their code.


2. One should not embed HTML in PHP, nor embed PHP in HTML. This is a special case of my general belief in separating application logic from presentation logic. There are several template engines for PHP (Smarty being my engine of choice), and there is no reason that I can see not to use them. It enhances the readability of your code, which is important when you or someone else goes back and looks at it two years later.


3. Indent your code. Indentation and appropriate use of whitespace make code very readable, and it's important that you and other people be able to read your code.


4. Comment your code. I use phpDocumentor because it generates nicely formatted HTML documentation. Commenting your code gives the reader some idea of whatever it is the code is supposed to do.


5. Document your code's public interface. This is sort of a special case of the previous item. Define the way you want your code to be interfaced with. Once your public interface is defined, then you can go and change anything behind the scenes to your heart's content, so long as it stays compatible with the public interface. This also means that if someone uses some undocumented feature of your code, and said undocumented feature goes away, the onus is on the caller to fix their code.


6. Don't use undocumented features of your or anyone else's code. That's just a recipe for disaster, for similar reasons as described in the previous item.