Justin Clark-Casey (justincc) a82bd5678e Use an integer when specifying the XWorkItem wait rather than a TimeSpan to avoid a Windows casting issue in SmartThreadPool for large TimeSpans. ... TimeSpan.Milliseconds is an int64. However, STP casts this to an int (32-bit). If TimeSpan.MaxValue is given then the casting results in an invalid value for the SDK WaitHandle.WaitAll() call. This was causing the co-op script termination regression tests to fail on Windows but not Mono 2.10.8 (which is perhaps not strict in the negative values that it accepts). Solution here is to use the int millisecondsTimeout STP call rather than the TimeSpan one. This also allows us to more clearly specify Timeout.Infinite rather than TimeSpan.MaxValue Thanks to Teravus for this spot.		2013-02-12 21:34:12 +00:00
..
ICompiler.cs	Optimizations	2009-10-29 05:39:18 -07:00
IScript.cs	Another stab at cmickeyb's patch for script GC.	2009-08-07 20:43:23 +01:00
IScriptApi.cs	Pass narrower WaitHandle rather than EventWaitHandle as co-op termination wait handle to script APIs.	2013-01-23 23:38:08 +00:00
IScriptEngine.cs	If ScriptStopStrategy hasn't been set to co-op in [XEngine] config, then continue to generate C# that is functionality identical to historical generation	2013-01-23 02:36:43 +00:00
IScriptInstance.cs	Use an integer when specifying the XWorkItem wait rather than a TimeSpan to avoid a Windows casting issue in SmartThreadPool for large TimeSpans.	2013-02-12 21:34:12 +00:00