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

deploy: 38a19d75d8

Browse source
This commit is contained in:
JesperSchulz 2021-12-15 09:08:17 +00:00
parent d4c41c7a00
commit 9c6169cd6c
175 changed files with 3887 additions and 3412 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>CASE Action on next line</title><link>https://alguidelines.dev/bcbestpractices/readability/case-actions/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://alguidelines.dev/bcbestpractices/readability/case-actions/</guid><description>&amp;lt;Created by Microsoft, Described by waldo&amp;gt;
Description A CASE action should start on a line after the possibility.
Bad code case Letter of &amp;#39;A&amp;#39;: Letter2 := &amp;#39;10&amp;#39;; &amp;#39;B&amp;#39;: Letter2 := &amp;#39;11&amp;#39;; end; Good code case Letter of &amp;#39;A&amp;#39;: Letter2 := &amp;#39;10&amp;#39;; &amp;#39;B&amp;#39;: Letter2 := &amp;#39;11&amp;#39;; 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>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.