From fff2febf8c7e57492b267636e95b3895f0543aa3 Mon Sep 17 00:00:00 2001 From: Steve Huston Date: Thu, 14 Apr 2005 21:05:27 +0000 Subject: ChangeLogTag:Thu Apr 14 15:25:31 2005 Steve Huston --- ChangeLog | 6 ++++++ NEWS | 11 +++++++++++ 2 files changed, 17 insertions(+) diff --git a/ChangeLog b/ChangeLog index 687286a6833..a396fd9be67 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,5 +1,11 @@ Thu Apr 14 15:25:31 2005 Steve Huston + * NEWS: Added a note that the reactor change: + Wed Apr 13 14:34:12 UTC 2005 Martin Corino + may cause some trouble in programs that dynamically allocate + a reactor implementation then destroy it before the ACE_Reactor + referring to it. This is always bad, but now will cause a crash. + * examples/Reactor/WFMO_Reactor/run_test.pl: Removed the "require Process" line - it tried to refer to the one in $ACE_ROOT/bin, which was removed: diff --git a/NEWS b/NEWS index 3e16a60f4bf..237fbbaa000 100644 --- a/NEWS +++ b/NEWS @@ -21,6 +21,17 @@ USER VISIBLE CHANGES BETWEEN ACE-5.4.4 and ACE-5.4.5 . Added support for GNU G++ 4.0. +. The ACE_Reactor destructor will now call close() on the referenced reactor + implementation. This assures that all handlers are notified before the + ACE_Reactor object that's most likely referenced in these handlers is + invalid. Although this should not be a user-visible change, it did catch + some ACE tests off guard destroying reactor implementations and ACE_Reactor + interfaces in the wrong order, so it may come up in the field as well. + When using dynamically allocated reactor implementations, do not destroy + the implementation object before the ACE_Reactor interface object. Use of + the ACE_Reactor constructor's delete_implementation argument (with a value + of 1) is recommended when dynamically allocating reactor implementations. + USER VISIBLE CHANGES BETWEEN ACE-5.4.3 and ACE-5.4.4 ==================================================== -- cgit v1.2.1