RE: Binding Directories -- MIDRANGE-L

× 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.

Title: RE: Binding Directories

I see that growing to be too large to try to maintain. Too hard to search/edit/organize binding directories.

Christopher K. Bipes    mailto:ChrisB@Cross-Check.com
Sr. Programmer/Analyst mailto:Chris_Bipes@Yahoo.com
CrossCheck, Inc.        http://www.cross-check.com
6119 State Farm Drive   Phone: 707 586-0551 x 1102
Rohnert Park CA 94928 Fax: 707 586-1884

If consistency is the hobgoblin of little minds, only geniuses work here. Karen Herbelin - Readers Digest 3/2000

-----Original Message-----
From: Scott Klement [mailto:klemscot@klements.com]
Sent: Friday, January 12, 2001 12:13 PM
To: Midrange-L (E-mail)
Subject: Re: Binding Directories

I'm confused. Why don't you just create a single binding directory that
contains all the service programs and modules listed in all the other
binding directories?

The binding directory is only used at bind time to determine which service
programs to search for procedures in. Simply adding all the service
programs to a single binding directory would have the same result as a
"binding directory of binding directories"

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.