Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!mailrus!tut.cis.ohio-state.edu!rutgers!bellcore!texbell!uhnix1!sugar!peter
From: peter@sugar.uu.net (Peter da Silva)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Manx help
Message-ID: <2939@sugar.uu.net>
Date: 1 Nov 88 12:34:43 GMT
References: <8810311911.AA06094@cory.Berkeley.EDU>
Organization: Sugar Land Unix - Houston, TX
Lines: 24

In article <8810311911.AA06094@cory.Berkeley.EDU>, dillon@CORY.BERKELEY.EDU (Matt Dillon) writes:
> 	ParentDir() returns a NEW LOCK, right?  Therefore, you *MUST*
> UnLock the lock returned by ParentDir() eventually before exiting.

Yeh, that's what I said.

> >[Unlocking your original lock] You should only do this
> >if you're writing a replacement to CD.

> 	No you can't!

If you're writing a replacement for "CD", you certainly can. This is the only
situation in which you should do something like this, of course. If your
program calls "CD" it's got to expect that its current directory is going
to be changed.

> 	Forgive the lack of error checking in line 4 of this example:

[ example that's basically identical to the example I gave, except it has
  less error checking than mine, deleted ]
-- 
		Peter da Silva  `-_-'  peter@sugar.uu.net
		 Have you hugged  U  your wolf today?

	Disclaimer: I accept full responsibility for my own typos.