Message-ID: <1622184881.10379.1419293526900.JavaMail.firstname.lastname@example.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_10378_981905547.1419293526900" ------=_Part_10378_981905547.1419293526900 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
These are ideas for things the boo compiler could check, using a= special compiler step. It is similar to pychecker or pylint. See also the = Boo Optimizations page.
No mixing of tabs and spaces for indentation.
The indentation s= cheme that we have now can cause problems by mixing spaces and tabs.
The code above will not
assert false because a space =
is hidden inside the indentation tabs.
The best way in my opinion to = handle this situation is to eliminate spaces as indentation altogether, but= an alternate situation would be to stop indentation from working in the ca= se that spaces and tabs are mixed.
if (i =3D=3D 2):.
fxCop might have some other ideas for things boo coul= d check.