[interfacekit] Re: BAutolock::Unlock()
- From: Tyler Dauwalder <tyler@xxxxxxxxxxxxx>
- To: interfacekit@xxxxxxxxxxxxx
- Date: Wed, 10 Sep 2003 17:24:44 -0700
On 2003-09-10 at 16:06:58 [-0700], Ingo Weinhold wrote:
> On 2003-09-11 at 00:34:33 [+0200], DarkWyrm wrote:
> > > since the list doesn't seem to be open for general subscription yet,
> > > I
> > > forward a request of Waldemar Kornewald's regarding the addition of a
> > > BAutolock::Unlock() method. It would be implemented inline and hence
> > > not
> > > even render apps using it R5 binary incompatible.
> > >
> > > Opinions?
> > I'm inclined to go with your ObjectLocker.h suggestion. It just seems
> > to me like AutoLockers should also be AutoUnlockers without the Unlock
> > method. I guess that's what BLockers are for. My $0.02. :^)
>
> Oh, don't misunderstand that -- the normal BAutolock semantics wouldn't
> change at all. Unlock() would be an additional feature to allow unlocking
> before the object is destroyed.
It sounds like a good idea to me, provided the intent for Unlock() is
clearly documented.
-Tyler
- References:
- [interfacekit] Re: BAutolock::Unlock()
- From: DarkWyrm
- [interfacekit] Re: BAutolock::Unlock()
- From: Ingo Weinhold
Other related posts:
- » [interfacekit] BAutolock::Unlock()
- » [interfacekit] Re: BAutolock::Unlock()
- » [interfacekit] Re: BAutolock::Unlock()
- » [interfacekit] Re: BAutolock::Unlock()
- [interfacekit] Re: BAutolock::Unlock()
- From: DarkWyrm
- [interfacekit] Re: BAutolock::Unlock()
- From: Ingo Weinhold