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

deploy: 4e0008525e

Browse source
This commit is contained in:
TheDoubleH 2021-12-14 21:32:47 +00:00
parent a135d8b92c
commit 723ebe0f8c
173 changed files with 3845 additions and 3373 deletions
Download patch file Download diff file Expand all files Collapse all files

5
bcbestpractices/readability/index.xml
View file

@ -14,7 +14,10 @@ Description The end else pair should always appear on the same line.
Bad code if OppEntry.Find('-') then if SalesCycleStage.Find('-') then begin ... end else ... end; Good code if OppEntry.Find('-') then if SalesCycleStage.Find('-') then begin ... end else ... end; Discussions You can find discussions on all “Best Practices” 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;
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>Line Start Keywords</title><link>https://alguidelines.dev/bcbestpractices/readability/line-start-keywords/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://alguidelines.dev/bcbestpractices/readability/line-start-keywords/</guid><description>&amp;lt;Created by Microsoft, Described by waldo&amp;gt;
Description The end, if, repeat, for, while, else and case statement should always start a line.
Bad code if IsContactName then ValidateContactName() else if IsSalespersonCode then ValidateSalespersonCode() else if IsSalesCycleCode then ValidatSalesCycleCode(); Good code if IsContactName then ValidateContactName() else if IsSalespersonCode then ValidateSalespersonCode() else if IsSalesCycleCode then ValidatSalesCycleCode(); 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>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;
Description The repeat statement should always be alone on a line.
Bad code if ReservEntry.FindSet() then repeat Good code if ReservEntry.FindSet() then repeat 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>Named Invocations</title><link>https://alguidelines.dev/bcbestpractices/readability/named-invocations/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://alguidelines.dev/bcbestpractices/readability/named-invocations/</guid><description>&amp;lt;Created by Microsoft, Described by waldo&amp;gt;