Added a note about one known weakness that arises from the wonderful complexity of asynchronous execution.

git-svn-id: https://samskivert.googlecode.com/svn/trunk@1555 6335cc39-0255-0410-8fd6-9bcaacd3b74c
2004-12-22 19:53:39 +00:00
parent 77f9c0fa11
commit ccd1e2a278
1 changed files with 7 additions and 0 deletions
@@ -139,6 +139,13 @@ public abstract class Interval
            return;
        }

+        // It's possible that we've been queued up on the RunQueue, and while
+        // we've been queued up the Interval was cancelled, rescheduled, and
+        // has fired again, in which case this run method will succeed even
+        // though it probably shouldn't. It's not the end of the world,
+        // this one will run and the new one that got queued up afterwards
+        // won't. I'm not sure if there's a way around that.
+
        // increment expired and scoot everything back if we're getting too big
        _expired++;
        if (_expired > Integer.MAX_VALUE/2) {