Kevin Atkinson [EMAIL PROTECTED] writes:
Feedback on the idea or implementation welcome. This code, at the moment,
does not follow boost standards. If people think it is a worthy addition
to boost I will be willing to being it up to boost standards. But for
right now please refrain from
This is my final repost of my Lock Classes. If I do not get any
constructive feedback this time I am going to give up.
These classes have the following features:
1) The ability to acquire a lock and release it when the object
goes out of scope effectively implementing the Monitor
[The attachment got messed up in the last post. Hopefully, it will be OK
this time]
This is my final repost of my Lock Classes. If I do not get any
constructive feedback this time I am going to give up.
These classes have the following features:
1) The ability to acquire a lock and release
On Wed, 19 Feb 2003, William E. Kempf wrote:
First off, just in case you didn't realize it, this message was directed at
one person not the group in general. I cced it to the list. I *hate*
forced reply-to.
Are you, or are you not interested in my Lock Classes. The messages I
got from
I posted this a couple days ago and have yet to seen any sort of reply or
any sign that anyone is interested. If people are having trouble
understanding the concept please let me know and I will try harder to
explain it. If you meant to reply but haven't yet, sorry for being
impatient.
If
Kevin, we're currently in the middle of a release and a formal review...
If you wait a week or so.. and recall our attention, you're likely to get a
response.
Just hold on.
Thanks,
Fernando Cacciola
___
Unsubscribe other changes:
On Tue, 18 Feb 2003, Fernando Cacciola (Home) wrote:
Kevin, we're currently in the middle of a release and a formal review...
If you wait a week or so.. and recall our attention, you're likely to get a
response.
Just hold on.
No problem. I'm in no rush. If I don't get any response
Attached is a series of lock I created for one of my projects. These
classes have the following features.
1) The ability to acquire a lock and release it when the object
goes out of scope effectively implemented the Monitor concept.
2) Avoid the need for recursive locks by careful
