while ( mChotin.tasks > Tasks.TooBloodyMany ) {

            switch ( Math.ceil( Math.random() * 4 ) ) ) {

                        case 1:

                                    mChotin.getLastTask().handoverToLackey();

                                    break;

                        case 2:

                                    mChotin.getLastTask().discoverToBeUncessary();

                                    break;

                        case 3:

                                    mChotin.getLastTask().finishInHalfTheTime();

                                    break;

                        case 4:

                                    mChotin.getLastTask().findABetterWayToDoIt();

                                    break;

            }

}

 

J bloody outlook ‘send email’ shortcut keys …

 


From: Matt Chotin [mailto:[EMAIL PROTECTED]
Sent: 14 February 2005 08:11PM
To: flexcoders@yahoogroups.com
Subject: RE: [flexcoders] RE: RE: Asynchrony problem?

 

It’s still going to be a number of days before I can write something up.  I need to

a)      verify that the implementation I did is useful for the team here

b)      write up an explanation of what I did and why I did it that way

c)      potentially do the port to 1.5

 

At the moment I only have time for (a)J

 

Sorry, I’m juggling a lot of balls right now…

 

Matt

 


From: Steven Webster [mailto:[EMAIL PROTECTED]
Sent: Monday, February 14, 2005 1:02 AM
To: flexcoders@yahoogroups.com
Subject: RE: [flexcoders] RE: RE: Asynchrony problem?

 

Hi guys,

 

 However, we are looking forward to seeing Matt’s implementation with FlexUnit under Flex 1.5. 

 

There's nothing Matt is doing that is required for Flex 1.5 - FlexUnit will work just fine with

Flex 1.5 as itis; and the various strategies that have been presented for testing asynchronous

calls work just fine.  We debated whether this belonged in the FlexUnit package or not, and

decided against forthe 1.0 release, as there are a number of strategies for testing asynchronous

calls (as you've all shown) and no single strategy seems to stand out as "the way it shouldbe

done".

 

I would imagine Matt is staring into a different crystal ball than us....

 

Steven

 

--

Steven Webster
Technical Director

iteration::two

 

This e-mail and any associated attachments transmitted with it may contain confidential information and must not be copied, or disclosed, or used by anyone other than the intended recipient(s). If you are not the intended recipient(s) please destroy this e-mail, and any copies of it, immediately.
 
Please also note that while software systems have been used to try to ensure that this e-mail has been swept for viruses, iteration::two do not accept responsibility for any damage or loss caused in respect of any viruses transmitted by the e-mail. Please ensure your own checks are carried out before any attachments are opened.

 

 

Reply via email to