Re: Container reqs

["Marin David Condic" <dont.bother.mcondic.auntie.spam@[acm.org>]

Seems like that might unreasonably lock up access to some object. Also, it
isn't clear to me how this would make the object task safe? Assume you have
a class that the constructor/destructor acquire some semaphore. It gets
globally declared such that two threads can access its functions. Does each
thread have to check/acquire the semaphore before write operations? Or do
you code a check of the semaphore into all the critical paths? It isn't
clear to me how this is supposed to work....

You could obviously do some sort of acquisition with controlled types - they
provide the same sort of capabilities of constructors/destructors - but why
would you want to if you have protected types?

MDC
--
Marin David Condic
Senior Software Engineer
Pace Micro Technology Americas    www.pacemicro.com
Enabling the digital revolution
e-Mail:    marin.condic@pacemicro.com
Web:      http://www.mcondic.com/


"Jean-Marc Bourguet" <jbourguet@free.fr> wrote in message
news:3bded21b$0$32589$626a54ce@news.free.fr...
>
> Ada can do it as well as C++ -- see controlled types.  (For cla people
> unused to RAII, it is the idiom where the constructor acquire a
> ressource and the destructor free it).
>
> But if you want to use it, you have to rely on the user to acquire the
> lock, so instead you define a new type providing only protected
> operation, like in Ada.
>