From 03c328bef95d20385b97541bba1434cdc042827c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Stefan=20Maro=C5=84?= Date: Wed, 15 Dec 2021 07:53:24 +0100 Subject: [PATCH] end; should also have a begin --- content/BCBestPractices/Readability/end-else-pair/index.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/content/BCBestPractices/Readability/end-else-pair/index.md b/content/BCBestPractices/Readability/end-else-pair/index.md index 88511484..c654ebf0 100644 --- a/content/BCBestPractices/Readability/end-else-pair/index.md +++ b/content/BCBestPractices/Readability/end-else-pair/index.md @@ -17,6 +17,7 @@ The `end else` pair should always appear on the same line. ... end else + begin ... end; ``` @@ -27,7 +28,7 @@ The `end else` pair should always appear on the same line. if OppEntry.Find('-') then if SalesCycleStage.Find('-') then begin ... - end else + end else begin ... end; ``` @@ -36,4 +37,4 @@ The `end else` pair should always appear on the same line. You can find discussions on all "Best Practices" [here](https://github.com/microsoft/alguidelines/discussions/categories/bc-best-practices). -If you don't find the discussion of this guideline, please feel fee to create a new one with the same title as this article. \ No newline at end of file +If you don't find the discussion of this guideline, please feel fee to create a new one with the same title as this article.