|
Scott summarized his viewpoints with the following, which my statementcame
from...
" Let's face it, folks... the only reason QTEMP needs to be in the library
list (aside from adding it on-the-fly for testing code) is because of
all the poorly written software out there. In this market space, poorly
written software absolutely ABOUNDS -- or, at least, that's been my
experience."
So maybe I should instead respond with this: Scott, do you think QTEMP
should NOT be used for temporary objects that a programmer wants to have
auto-cleaned-up at the end of the job? I thought there were good points on
why a vendor wouldn't want to use QTEMP. Many times I rely on QTEMP when I
am doing professional services contracts, and so far it has worked quite
well for me. I would chalk QTEMP usage up to "it depends" and "use it to
your benefit, but understand the drawbacks".
Thoughts?
Aaron Bartell
http://mowyourlawn.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.