Leica tps1100, Руководство пользователя, Страница: 45 / 1154

GeoBASIC User Manual 8 — Typical GeoBASIC Programming
8-12 TPS1100-Version 2.10
SUB LabelExample ()
'code of the procedure
LabelExample_Err:
SELECT CASE ERR
'handle specific errors here
CASE ELSE
'generic error handler here
END SELECT
END LabelExample
8.3.6 Remark on naming conventions
Naming conventions never replace the judicious use of comments in your
GeoBASIC program code. Naming conventions are an extension of, not a
replacement for, good program-commenting techniques.
Formulating, learning, and applying a consistent naming style require a significant
initial investment of time and energy. However, you will be amply rewarded when
you return to your application a year later to do maintenance or when you share
your code with others. Once you implement standardised names, you will quickly
grow to appreciate the initial effort you made.
To complete the discussion about naming conventions, we mention the use of
program headers:
In every function/subprocedure there should be a header describing, at a minimum,
purpose, and parameters passed and/or returned. (In addition there might be
comments, the author's name, last revision date, notes, etc.)