[Swift-devel] Re: karajan futures and getfieldvalue/setfieldvalue

[Ben Clifford]

On Sun, 16 Nov 2008, Ben Clifford wrote:

> It looks like if SetFieldValue throws a FutureNotYetAvailable exception, 
> then this does not have the same behaviour of deferring execution and 
> rerunning later, as when GetFieldValue throws a FutureNotAvailable 
> exception which seems to work ok.

I played with this today and made it go away. SetFieldValue was actually 
incorrectly catching the FutureNotYetAvailable exception (as part of 
catching all Exceptions) and then throwing an ExecutionException with no 
message set. That ExecutionException was displayed in a way that is 
confusingly like the exception it wraps.

A simple fix was to make this catch FutureNotYetAvailable and rethrow it. 
Probably the catch of all Exceptions should be tightened up.

I'll commit code for this later today.

--