FreeLists / openbeosnetteam / [openbeosnetteam] Re: moving ppp to other location

[Ingo Weinhold <bonefish@xxxxxxxxxxxxxxx>]

On 2003-09-08 at 19:06:49 [+0200], Waldemar Kornewald wrote:
> > > To BAutolock:
> > > The current implementation is missing a call:
> > > UnlockNow(). This method is used quite frequently in PPP.
> > > What does it do? It unlocks the BLocker before the destructor was
> called.
> > > I have changed the implementation in my repository to support this
> feature
> > > (it is only slightly bigger than the current implementation because the
> > > destructor can use UnlockNow(), too).
> > > You probably do not like the name. :) Is Unlock() better?
> > > Shall I commit the change?
> >
> > Unlock() is better, I think. Anyway, you should propose this on the IK
> team
> > list. If there's agreement on the name, it should be no problem to add it,
> > since it would be inline anyway, so that apps can use it without losing R5
> > compatibility.
> 
> I thought the IK team list is private (or did this change already?). Could
> you do this for me, please?

Sorry, I'm too lazy. ;-)
Looks like the list is open, anyway:
http://www.freelists.org/cgi-bin/list?list_id=interfacekit

> Would a Lock() method be needed, too?

You mean to re-lock after unlocking? Doesn't make that much sense to me. 
What, I think, may make some more sense is a flag to the constructor 
indicating that the object shall not acquire a lock, but just assume that the 
caller has a lock and wants to transfer it. The converse functionality could 
be available as well, i.e. a method Unset() that doesn't unlock, but just 
uninitialize the object.

CU, Ingo