summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authornanbor <nanbor@ae88bc3d-4319-0410-8dbf-d08b4c9d3795>1998-08-20 01:54:32 +0000
committernanbor <nanbor@ae88bc3d-4319-0410-8dbf-d08b4c9d3795>1998-08-20 01:54:32 +0000
commit66ac24eab86dc44705ef35556b7f075dc43a9c9e (patch)
tree05992dfa7ca5a6a8aceab7577edb41b3a6acc64f
parentdb4e86b332fa6b2f26fc6866adeac38925042c10 (diff)
downloadATCD-66ac24eab86dc44705ef35556b7f075dc43a9c9e.tar.gz
*** empty log message ***
-rw-r--r--ChangeLog-98b20
1 files changed, 20 insertions, 0 deletions
diff --git a/ChangeLog-98b b/ChangeLog-98b
index 0e510eae7cd..143b4a0c728 100644
--- a/ChangeLog-98b
+++ b/ChangeLog-98b
@@ -1,3 +1,23 @@
+Wed Aug 19 20:34:25 1998 Nanbor Wang <nanbor@cs.wustl.edu>
+
+ * ace/README:
+ * ace/OS.h: Added a new macro directive
+ "ACE_DONT_INSTANTIATE_NONSTATIC_OBJECT_MANAGER". By defining
+ this macro, it implicitly forces ACE to use non-static object
+ manager and _NOT_ instantiating ACE_Object_Manager for you and
+ assumes you will take the responsibility of instantiating
+ ACE_Object_Manager at the proper place in your programs. This
+ is usually used when using ACE with MFC/Windows programs.
+ Because the main function is defined by MFC/Windows libraries,
+ ACE has no way to instantiate object manager in these programs.
+ For programs using MFC, a good place to instantiate Object
+ Manger will be to define ACE_Object_Manager a member of
+ CApplication derived classes so it gets instantiated/destructed
+ properly.
+
+ * ace/config-win32.h: Revised the comment about
+ ACE_HAS_NONSTATIC_OBJECT_MANAGER
+
Wed Aug 19 17:15:00 1998 Douglas C. Schmidt <schmidt@tango.cs.wustl.edu>
* ace/Service_Config.cpp: Moved the registration of the SIGHUP