From 789a7467bba5edb2450fd7c2e16467aebd771a10 Mon Sep 17 00:00:00 2001 From: iliyan Date: Tue, 31 Jul 2007 21:32:59 +0000 Subject: Tue Jul 31 21:27:25 UTC 2007 Iliyan Jeliazkov --- ACE/ace/Service_Config.cpp | 19 ------------------- 1 file changed, 19 deletions(-) (limited to 'ACE/ace/Service_Config.cpp') diff --git a/ACE/ace/Service_Config.cpp b/ACE/ace/Service_Config.cpp index 5b911585a6a..c4d6d005f18 100644 --- a/ACE/ace/Service_Config.cpp +++ b/ACE/ace/Service_Config.cpp @@ -362,25 +362,6 @@ ACE_Service_Config::resume (const ACE_TCHAR svc_name[]) return ACE_Service_Repository::instance ()->resume (svc_name); } -// This specialization allows us to have an ACE_TSS, which will _not_ perform -// a delete on (ACE_Service_Gestalt*) p up on thread exit, when TSS is -// cleaned up. -// Note that the tss_ member will be destroyed with the ACE_Object_Manager's -// ACE_Service_Config singleton, so no leaks are introduced. -template<> -void -ACE_TSS::cleanup (void* ptr) -{ - // We need this because the SC instance is really owned by the Object - // Manager and the TSS cleanup must not dispose of it prematurely. - // Naturally, things would be simpler, if we could avoid using the TSS - // altogether but we need the ability to temporarily designate a - // different SC instance as the "default." So, the solution is a hybrid, - // or non-owner ACE_TSS. - // See ticket 2980 for a description of a test case where - // ACE_TSS::cleanup() is called before ~ACE_Object_Manager. -} - ACE_Service_Config::ACE_Service_Config (int ignore_static_svcs, size_t size, -- cgit v1.2.1