Procedure naming conventions (WAS: Validate client name)

For my programming style, I have moved away from the 3A abbreviations as
much as is feasible, because abbreviations do not read like a book. You
are inserting one more abstraction/roadblock in the path that our brain
must process to understand the code.

I admit that I do like a 3A prefix to show the designation of which
module the procedure came from. But after that, it reads like a
function described in English terms, not aFuncDesInEngTrm.

Also, for readability, I created a standard helper proc of functions
like "IsBlank( var )" instead of "var <> *blank".
(This may read more like Visual Basic, but you know what, Visual Basic
was and still is more popular than RPG.)
And from Domain Driven Design theory, what we are really doing when we
use "key <> 0" is asking "Is key entered and is it a valid entity". So
our function shouldn't even be "IsZero( key )" but "IsEntity( key : file
)".

Lastly, I applaud all the considerations and opinions brought to this
discussion of RPG style, since we still have a long way to go to make
the RPG code base in corporations a modern dialect that our descendents
will find valuable.

numeric component tells you precisely NOTHING about what this

procedure does.

I like to choose names that seem to make sense when you read them in
code, like "Clt_NameIsValid" and "Com_NameIsValid". In use, your
code reads like a book: