summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorirfan <irfan@ae88bc3d-4319-0410-8dbf-d08b4c9d3795>1997-12-15 07:16:07 +0000
committerirfan <irfan@ae88bc3d-4319-0410-8dbf-d08b4c9d3795>1997-12-15 07:16:07 +0000
commit7f5e003ad112a5486a42a40cb66ff9e7e39c4f60 (patch)
tree45d88c017ab5771db2ed3ff780d04a5ba2baff10
parent70acb4837fa044641733d8ec42efc703c9a95f99 (diff)
downloadATCD-7f5e003ad112a5486a42a40cb66ff9e7e39c4f60.tar.gz
*** empty log message ***
-rw-r--r--ChangeLog-98a8
-rw-r--r--ace/Atomic_Op.i10
-rw-r--r--ace/Synch_T.h6
3 files changed, 24 insertions, 0 deletions
diff --git a/ChangeLog-98a b/ChangeLog-98a
index 31221b10f25..4b7748a0f84 100644
--- a/ChangeLog-98a
+++ b/ChangeLog-98a
@@ -1,3 +1,11 @@
+Mon Dec 15 01:12:33 1997 <irfan@TWOSTEP>
+
+ * ace/Synch_T.h (ACE_Atmoic_Op::value_i): Explicitly return
+ <value_> (by reference). This gives the user full, unrestricted
+ access to the underlying value. This method will usually be
+ used in conjunction with explicit access to the lock. Use with
+ care ;-)
+
Sun Dec 14 21:37:08 1997 Douglas C. Schmidt <schmidt@tango.cs.wustl.edu>
* ace/OS.i (cond_wait,cond_timedwait): Fixed a missing return to
diff --git a/ace/Atomic_Op.i b/ace/Atomic_Op.i
index e405007406f..8c56bb42ba2 100644
--- a/ace/Atomic_Op.i
+++ b/ace/Atomic_Op.i
@@ -123,6 +123,16 @@ ACE_Atomic_Op<ACE_LOCK, TYPE>::value (void) const
return this->value_;
}
+template <class ACE_LOCK, class TYPE> ACE_INLINE TYPE &
+ACE_Atomic_Op<ACE_LOCK, TYPE>::value_i (void)
+{
+ // Explicitly return <value_> (by reference). This gives the user
+ // full, unrestricted access to the underlying value. This method
+ // will usually be used in conjunction with explicit access to the
+ // lock. Use with care ;-)
+ return this->value_;
+}
+
template <class ACE_LOCK, class TYPE> ACE_INLINE void
ACE_Atomic_Op<ACE_LOCK, TYPE>::operator= (const TYPE &i)
{
diff --git a/ace/Synch_T.h b/ace/Synch_T.h
index ca5172afc2b..b97ce1cbb2f 100644
--- a/ace/Synch_T.h
+++ b/ace/Synch_T.h
@@ -212,6 +212,12 @@ public:
// <ACE_Recursive_Mutex>.
// NOTE: the right name would be lock_, but HP/C++ will choke on that!
+ TYPE &value_i (void);
+ // Explicitly return <value_> (by reference). This gives the user
+ // full, unrestricted access to the underlying value. This method
+ // will usually be used in conjunction with explicit access to the
+ // lock. Use with care ;-)
+
private:
ACE_LOCK mutex_;
// Type of synchronization mechanism.