phsjhxx

5. Language Usage
The language usage section is partly based on the rules defined within the tool CodeXpert
by Quest Software (www.quest.com). All text taken directly from this source is marked by
(CodeXpert). Every rule, that may be checked by CodeXpert ist marked with a red label
including the rule number within CodeXpert.
5.1. General
1. Try to label your sub blocks.
[CodeXpert 4403]
2. Always have a matching loop or block label.
[CodeXpert 4403]
Reason: Use a label directly in front of loops and nested anonymous blocks:
• To give a name to that portion of code and thereby selfdocument
what it is doing.
• So that you can repeat that name with the END statement of that
block or loop.
Example:
-- Good
BEGIN
BEGIN
…;
END prepare_data;
…
END;
BEGIN
…
END process_data;
3. Avoid defining variables that are not used.
[CodeXpert 6405]
4. Avoid dead code in your programs.
[CodeXpert 6801]
Reason: Any part of your code, which is no longer used or cannot be reached,
should be eliminated from your programs.
5. Avoid using literals in your code.
[CodeXpert 4602]
Reason: Literals are often used more than once in your code. Having them defined
as a constant reduces typos in your code.
All constants should be collated in just one package used as a library. If
these constants should be used in SQL too it is good practice to write a
get_ deterministic package function for every constant.
PL/SQL Coding Guidelines 17