Re: Qualified procedure names

["John Taylor" <jtaylor@xxxxxxxxxxxx>]

Buck,


> This has bit me only once so far, but I am The One who uses service
programs
> here so far.  Once (oh, please make it soon!) other folks get into the
> habit, I would guess that collisions will be more frequent.

Not surprisingly, you're managing better than I am. :)

For example, one of the more common functions (oops! procedures) that I
include in a service program is "find()". Now, instead of just calling it
find(), I have to waste my time dreaming up name that will be:

1) long enough to be meaningful
2) short enough to be useable
3) unique across my system namespace (God forbid I'm a contractor!)

Well, the first two criteria are immediately satisfied, but the third one
requires me to search through my source library in order to ensure that
it'll be unique. So I end up with functions like this:

findDataQueue()
findUserSpace()
findSalesOrder()
findSlsOrdItm()
findPurchOrder()
findPchOrdItm()

That's painful enough, but it get's worse with functions like
"getDescription()". Virtually all business related data carries some type of
description, but this common function name ends up as:

getDQDesc()
getUSPDesc()
getSODesc()
getSOIDesc()
getPODesc()
getPOIDesc()

or, alternatively:

so_find()
so_getDesc()
po_find()
po_getDesc()


Like I said, it affects me every single day, in virtually every program I
write.


John Taylor