×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Chuck
Thanks for the reply - here's the bit that seems a little self-contradictory to me - in your first reply you said that the intent of using a PRDLIB was so you did NOT have to ADLDIBLE to get at things in your own library, that of your product. Am I mixing apples and oranges here? You suggest that there is no reason an application would want to run a system command against its own resources - that did not make sense to me.
I guess I'm thinking that the system DOES know what product libraries have been used - you mentioned an LIFO stack - that's what I assumed was the mechanism. One could always put a limit on the number of stack entries. So it is not IMpossible to know what those are, hence, they COULD be included in the search path. Now what are the side effects? Hey, I'm fighting my own issues with side effects in my own coding now!!! ;-)
Thanks
Vern
If a [utility
or] product is using the PRDLIB() to effect enabling the user to access
objects in that product library, my assertion is that having coded such
a dependency is a _design flaw_ for that product.
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.
midrange.com
