summaryrefslogtreecommitdiff
path: root/ChangeLog-98b
diff options
context:
space:
mode:
authorschmidt <douglascraigschmidt@users.noreply.github.com>1999-01-05 04:02:55 +0000
committerschmidt <douglascraigschmidt@users.noreply.github.com>1999-01-05 04:02:55 +0000
commit99c5f71e1d7f46468a247236f2ac0470e5e97e94 (patch)
tree8c49b901dfc85ce023d999362bbe7007bb8a6451 /ChangeLog-98b
parent6ae8f3ee75f41f01c0f22789590f608c87812938 (diff)
downloadATCD-99c5f71e1d7f46468a247236f2ac0470e5e97e94.tar.gz
*** empty log message ***
Diffstat (limited to 'ChangeLog-98b')
-rw-r--r--ChangeLog-98b13
1 files changed, 13 insertions, 0 deletions
diff --git a/ChangeLog-98b b/ChangeLog-98b
index 22302559e12..906d77d5f43 100644
--- a/ChangeLog-98b
+++ b/ChangeLog-98b
@@ -1,5 +1,18 @@
Mon Jan 4 13:00:07 1999 Douglas C. Schmidt <schmidt@ace.cs.wustl.edu>
+ * ace/Synch: Changed the remove() method of ACE_Thread_Mutex,
+ ACE_Mutex, ACE_Semaphore, ACE_RW_Mutex, ACE_Event,
+ ACE_Thread_Condition_Mutex, and ACE_Recursive_Thread_Mutex so
+ that they check a flag to see if remove() has already been
+ called. If it has, then the remove() call does nothing. This
+ avoids nasty problems on platforms like Win95 that fail
+ mysteriously if locks are destroyed multiple times. Note that
+ our solution isn't perfect since it won't protect against race
+ conditions if multiple threads call remove() simultaneously.
+ However, if this happens it's a sign that the application was
+ designed incorrectly... Thanks to Paul Felix <pef@fluent.com>
+ and Irfan for tracking this down.
+
* ace/FILE: Added new methods, seek() and tell(), that are more
intuitively named than the existing position() methods. The
position() methods have been retained for backwards