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

deploy: 56ac137f7c

Browse source
This commit is contained in:
TheDoubleH 2021-12-14 21:31:38 +00:00
parent 359c95bfac
commit a135d8b92c
172 changed files with 3824 additions and 3352 deletions
Download patch file Download diff file Expand all files Collapse all files

3
bcbestpractices/readability/index.xml
View file

@ -9,6 +9,9 @@ Bad code "Quantity to Ship" := Quantity - "Quantity Ship
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>end else pair</title><link>https://alguidelines.dev/bcbestpractices/readability/end-else-pair/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://alguidelines.dev/bcbestpractices/readability/end-else-pair/</guid><description>&amp;lt;Created by Microsoft, Described by waldo&amp;gt;
Description The end else pair should always appear on the same line.
Bad code if OppEntry.Find(&amp;#39;-&amp;#39;) then if SalesCycleStage.Find(&amp;#39;-&amp;#39;) then begin ... end else ... end; Good code if OppEntry.Find(&amp;#39;-&amp;#39;) then if SalesCycleStage.Find(&amp;#39;-&amp;#39;) then begin ... end else ... end; 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;