RE: QTEMP cleanup

<snip>
Finally, if none of these points sway you and you insist that you must
write
your software so that it can be installed in environments where the
library
list cannot be pre-determined, then the obvious answer is to save the
current library list, change to what you need, and then restore the
original
when you're done. I've done that a lot in my time.
<snip>


SSA did this with BPCS.





Thanx,

Nick



Nick Radich
Sr. Programmer/Analyst
EPC Molding, Inc.
Direct (320) 679-6683
Toll free (800) 388-2155 ext. 6683
Fax (320) 679-4516
nick_radich@xxxxxxxxxxxxxx



"Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
01/14/2008 11:22 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
"'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
cc

Subject
RE: QTEMP cleanup

From: Elvis Budimlic

I can tell you from experience that if you assume anything pertaining to
the system's environment, you'll inevitably be bitten in the ??? as some
shop's environment will differ.

(...snip...)

To summarize, use QTEMP in commercial software but make sure you
implicitly qualify its usage.

So do you hardcode every object reference? Because if you don't, how can
you assume that the user will have your non-QTEMP libraries in their
library
list? I think the concern that you have absolutely no control over the
library list is perhaps a little overstated.

I suppose the use of QTEMP specifically could be a problem if two of your
packages somehow conflict, with one needing QTEMP at the end of the
library
list and one needing it at the beginning. However, there's no good reason
to require a library be at the END of the library list. If its object
names
conflict with other objects in the library list, then the objects wouldn't
be found anyway unless you were hardcoding the library name, at which
point
you wouldn't need the library in your library list at all! And if they
don't conflict, it doesn't matter where the library is in the library
list.

Finally, if none of these points sway you and you insist that you must
write
your software so that it can be installed in environments where the
library
list cannot be pre-determined, then the obvious answer is to save the
current library list, change to what you need, and then restore the
original
when you're done. I've done that a lot in my time.

Joe