Re: [paragui-users] Puzzled newbie question

[Alexander Pipelka]

Am Mon, 2002-04-29 um 18.54 schrieb Andrew Ford:
> Whatever is done for this, it shouldn't be visible
> when you're writing new widgets or event code on the
> developer's side.  I think if you use reference
> counting, you should be able to do the locking inside
> the reference counter.  I'm reading a book "Modern C++
> Design, etc... etc..." by Andrei Alexandrescu.  One of
> the things he describes instantiating things like
> reference counters with "Policy" objects that define
> what checks or options take place inside the object. 
> For instance:
> 
> template < class checkingPolicy = noCheck, class
> threadPolicy = noLock > class refCounter
> {
>   whatever...
> }
> 
> Then, depending on how you wanted to build this
> object, you would instantiate with a functor object
> that locked this reference counter on access, or
> checked for access to null, or whatever else you
> wanted to do with this object.  I know this is
> offtopic :), but I thought it was a really interesting
> approach to this sort of thing.

No way offtopic :))

Can you imagine designing that stuff for 1.1.x ?

Alex