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

deploy: da9359cdb0

Browse source
This commit is contained in:
TheDoubleH 2021-12-14 21:21:42 +00:00
parent c636361aaf
commit 6ca52ea91a
169 changed files with 4193 additions and 3263 deletions
Download patch file Download diff file Expand all files Collapse all files

7
bcbestpractices/readability/index.xml
View file

@ -1,4 +1,9 @@
<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Readability on AL Guidelines</title><link>https://alguidelines.dev/bcbestpractices/readability/</link><description>Recent content in Readability on AL Guidelines</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><atom:link href="https://alguidelines.dev/bcbestpractices/readability/index.xml" rel="self" type="application/rss+xml"/><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;
<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Readability on AL Guidelines</title><link>https://alguidelines.dev/bcbestpractices/readability/</link><description>Recent content in Readability on AL Guidelines</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><atom:link href="https://alguidelines.dev/bcbestpractices/readability/index.xml" rel="self" type="application/rss+xml"/><item><title>begin as an 'After Word'</title><link>https://alguidelines.dev/bcbestpractices/readability/begin-as-an-afterword/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://alguidelines.dev/bcbestpractices/readability/begin-as-an-afterword/</guid><description>&amp;lt;Created by Microsoft, Described by waldo&amp;gt;
Description When begin follows then, else, do, it should be on the same line, preceded by one space character.
Bad code if ICPartnerRefType = ICPartnerRefType::&amp;#34;Common Item No.&amp;#34; then begin ... end; Good code if ICPartnerRefType = ICPartnerRefType::&amp;#34;Common Item No.&amp;#34; then begin ... 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>Begin-End - Compound Only</title><link>https://alguidelines.dev/bcbestpractices/readability/begin-end/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://alguidelines.dev/bcbestpractices/readability/begin-end/</guid><description>&amp;lt;Created by Microsoft, Described by waldo&amp;gt;
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>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;
Description The repeat statement should always be alone on a line.