http://docs.modxcms.com/modext/

See "Editor Settings and Spacing" under "MODx Coding Standards".

More to come.

Here’s an example of my proposal in action:

<?php
/**
 * Used only to demonstrate when to use spaces as opposed to
 * tabs when writing/indenting code.
 * 
 * "___>" = tab character
 * "...." = 4 space characters
 */
function example_function() {
___>if (true)
___>......return true;..// A comment that will span
___>else..return false;.// multiple lines
}

Coding in this manner will give each programmer their own control over how many spaces a tab should be interpreted as and also ensures that each programmer will see the code aligned the way it should be.

The main argument for tabs is to save bytes, but that argument goes out the window if you use spaces everywhere to line up text/comments.

And no, this isn’t Python, but the same issues apply regarding using various editors, some that are simply inept at dealing with the problem properly.

...

Regarding the 4 bytes vs 1 byte argument, I do agree the space savings could be important for objects being delivered to the browser, but I’m not convinced that this point trumps the other issues. But I’m certainly not going to block any dialog on the subject, so feel free to convince me otherwise, or override my veto...

<?php
/**
 * Used only to demonstrate when to use spaces as opposed to
 * tabs when writing/indenting code.
 * 
 * "___>" = tab character
 * "...." = 4 space characters
 */
function example_function() {
___>if (true)
___>......return true;..// A comment that will span
___>else..return false;.// multiple lines
}