Microsoft/alguidelines
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

deploy: d0bbfcebed

Browse source
This commit is contained in:
TheDoubleH 2021-12-14 21:24:50 +00:00
parent 51853c60ee
commit a1725fca7b
170 changed files with 3769 additions and 3312 deletions
Download patch file Download diff file Expand all files Collapse all files

3
bcbestpractices/readability/index.xml
View file

@ -6,6 +6,9 @@ Only use begin..end to enclose compound statements.
Bad code if FindSet() then begin repeat ... until next() = 0; end; Good code IF FindSet() then repeat ... until next() = 0; Bad code IF IsAssemblyOutputLine then begin TestField(&amp;#34;Order Line No.&amp;#34;,0); end; Good code IF IsAssemblyOutputLine then TestField(&amp;#34;Order Line No.&amp;#34;,0); Exception // Except for this case IF X then begin IF Y then //DO SOMETHING; end else (not X) Discussions You can find discussions on all &amp;ldquo;Best Practices&amp;rdquo; here.</description></item><item><title>Binary Operator to Start Line</title><link>https://alguidelines.dev/bcbestpractices/readability/binary-operator-line-start/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://alguidelines.dev/bcbestpractices/readability/binary-operator-line-start/</guid><description>&amp;lt;Created by Microsoft, Described by waldo&amp;gt;
Description Do not start a line with a binary operator.
Bad code &amp;#34;Quantity to Ship&amp;#34; := Quantity - &amp;#34;Quantity Shipped&amp;#34; Good code &amp;#34;Quantity to Ship&amp;#34; := Quantity - &amp;#34;Quantity Shipped&amp;#34; Discussions You can find discussions on all &amp;ldquo;Best Practices&amp;rdquo; here.
If you don&amp;rsquo;t find the discussion of this guideline, please feel fee to create a new one with the same title as this article.</description></item><item><title>Comment Spacing</title><link>https://alguidelines.dev/bcbestpractices/readability/comments-spacing/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://alguidelines.dev/bcbestpractices/readability/comments-spacing/</guid><description>&amp;lt;Created by Microsoft, Described by waldo&amp;gt;
Description Always start comments with // followed by one space character.
Bad code RowNo += 1000; //Move way below the budget Good code RowNo += 1000; // Move way below the budget Discussions You can find discussions on all &amp;ldquo;Best Practices&amp;rdquo; here.
If you don&amp;rsquo;t find the discussion of this guideline, please feel fee to create a new one with the same title as this article.</description></item><item><title>Keyword Pairs - Indentation</title><link>https://alguidelines.dev/bcbestpractices/readability/keyword-pairs-indentation/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://alguidelines.dev/bcbestpractices/readability/keyword-pairs-indentation/</guid><description>&amp;lt;Created by Microsoft, Described by waldo&amp;gt;
Description The if..then pair, while..do pair, and for..do pair must appear on the same line or the same level of indentation. If possible, you can align the lines it is even much more readable.
Bad code if (x = y) and (a = b) then Good code if (x = y) and (a = b) then Discussions You can find discussions on all &amp;ldquo;Best Practices&amp;rdquo; here.</description></item><item><title>Lonely Repeat</title><link>https://alguidelines.dev/bcbestpractices/readability/lonely-repeat/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://alguidelines.dev/bcbestpractices/readability/lonely-repeat/</guid><description>&amp;lt;Created by Microsoft, Described by waldo&amp;gt;