Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Message-ID: <4F321B14.3060700@leichtgewicht.at>
Date: Wed, 08 Feb 2012 15:49:56 +0900
From: Martin Heidegger <mh@leichtgewicht.at>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:10.0) Gecko/20120129 Thunderbird/10.0
MIME-Version: 1.0
To: flex-dev@incubator.apache.org
Subject: Re: [RT] From Singletons to Unit-testable code
References: <CB5756A6.3BB5B%aharui@adobe.com>
In-Reply-To: <CB5756A6.3BB5B%aharui@adobe.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit


On 08/02/2012 15:31, Alex Harui wrote:
> You can have a back-door to replace singletons if you want to.  That's even
> easier to add to Singleton. For now though, keep in mind that because of
> the stew of dependencies between classes in the framework, you really need
> to restart the app or implement a reset protocol, otherwise something might
> break when you replace a singleton after startup.
Of course replacing the singleton could break a running system. Once its 
all instances then a singleton can't break anything. But more 
importantly: I don't suggest that this "context-replacement" is used 
permanently. Its a refactoring strategy to get to a tested system 
without breaking code.

> folks trying to modify the framework as is, or folks who will help
> me with my re-write.

Uhm, how can folks help you?

yours
Martin.