home *** CD-ROM | disk | FTP | other *** search
- Nntp-Posting-Host: bert.cs.byu.edu
- Lines: 28
- Path: sparky!uunet!gatech!news.byu.edu!news
- Message-ID: <su#@byu.edu>
- Date: Mon, 11 Jan 93 16:37:47 MST
- From: dougc@bert.cs.byu.edu (Douglas R. Cannon)
- Organization: BYU, Provo, Utah
- Newsgroups: comp.sys.hp48
- Subject: Re: Library Trouble
- References: <C0JLMA.EsE@cs.dal.ca> <*u#@byu.edu>
- <2b51bf3b.2603.5comp.sys.hp48.1@hpcvbbs.cv.hp.com>
-
- In article <2b51bf3b.2603.5comp.sys.hp48.1@hpcvbbs.cv.hp.com> akcs.levenson@hpcvbbs.cv.hp.com (william j. levenson) writes:
-
- >I HAVE seen libraries that intentionally do not self attach. This is
- >probably so that the user can attach the library to whatever directory he
- >desires. This might be advantageous if you only wanted to be able to run
- >a certain library from a certain directory.
-
- True, but even a library that has no config object (and thus does not
- intentionally attach itself to the HOME directory) will be automatically
- attached to the HOME directory at the next warm start.
-
- So, if you want to only execute certain library functions from a certain
- directory, then you would attach that library to that sub-directory. Then,
- those library functions would only be visible in that sub-directory. However,
- at the next warm start the library is attached to the home directory (and
- also stays attached to your sub-directory) and now your library commands are
- visible everywhere.
-
- The only solution that I see (with my limited understanding) is to create
- a library that expressely detaches itself from the HOME directory at each
- warm start. This is great unless the user actually WANTS it to be attached
- to the HOME directory.
-
- Heck, I dunno. Any other thoughts? It makes this whole attach-detach
- thing look pretty useless to me since all libraries end up being attached
- to the HOME directory eventually. Am I missing something?
-
- Doug
-