diff options
| author | nanbor <nanbor@ae88bc3d-4319-0410-8dbf-d08b4c9d3795> | 1999-07-12 21:51:04 +0000 |
|---|---|---|
| committer | nanbor <nanbor@ae88bc3d-4319-0410-8dbf-d08b4c9d3795> | 1999-07-12 21:51:04 +0000 |
| commit | 1d3b607f2862df1a5ad891e26fdb98ec81ddc4d1 (patch) | |
| tree | 9d60a8d48fb4e17f74211d263285c85478fe80f9 /ace/config-win32.h | |
| parent | 8301abe4c7e8a2cab8e7d876ec5244bf03b626f3 (diff) | |
| download | ATCD-1d3b607f2862df1a5ad891e26fdb98ec81ddc4d1.tar.gz | |
Updated comments regarding non-static object managers.
Diffstat (limited to 'ace/config-win32.h')
| -rw-r--r-- | ace/config-win32.h | 27 |
1 files changed, 18 insertions, 9 deletions
diff --git a/ace/config-win32.h b/ace/config-win32.h index aaf43634f2c..ffaa4905968 100644 --- a/ace/config-win32.h +++ b/ace/config-win32.h @@ -166,19 +166,28 @@ // By default, we use non-static object manager on Win32. That is, // the object manager is allocated in main's stack memory. If this -// does not suit your need, you can disable the behavior by defining -// ACE_HAS_NONSTATIC_OBJECT_MANAGER to 0. +// does not suit your need, i.e., if your programs depend on the use +// of static object manager, you neet to disable the behavior by +// defining ACE_HAS_NONSTATIC_OBJECT_MANAGER=0. // -// MFC users: the main function is defined withing MFC library. -// Therefore, you'll need to instantiate the ACE_Object_Manager by +// MFC users: the main function is defined within a MFC library and +// therefore, ACE won't be able to meddle with main function and +// instantiate the non-static object manager for you. To solve the +// problem, you'll need to instantiate the ACE_Object_Manager by // either: // -// 1. Using static object manager (as described above). -// 2. #define ACE_DOESNT_INSTANTIATE_NONSTATIC_OBJECT_MANAGER in your -// ace/config.h, _and_ either 1) call ACE::init () at the beginning -// and ACE::fini () at the end, _or_ 2) instantiate the -// ACE_Object_Manager in your CApplication derived class. +// 1. Using static object manager (as described above), however, using +// the non-static object manager is prefered, therefore, +// 2. Instantiate the non-static object manager yourself by either 1) +// call ACE::init () at the beginning and ACE::fini () at the end, +// _or_ 2) instantiate the ACE_Object_Manager in your CApplication +// derived class. // +// Optionally, you can #define +// ACE_DOESNT_INSTANTIATE_NONSTATIC_OBJECT_MANAGER in your +// ace/config.h and always take care of the business by yourself. +// ACE_DOESNT_INSTANTIATE_NONSTATIC_OBJECT_MANAGER has no effect when +// using static object managers. #if !defined (ACE_HAS_NONSTATIC_OBJECT_MANAGER) # define ACE_HAS_NONSTATIC_OBJECT_MANAGER #elif (ACE_HAS_NONSTATIC_OBJECT_MANAGER == 0) |