Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-6402327

Clarify Condition.awaitNanos negative return value ambiguity

XMLWordPrintable

      From Doug Lea:

      >> We should probably make the ambigity for <= 0 returns explicit so other
      >> people
      >> don't mis-interpret this.
      >> How about:

      diff -c -r1.11 -r1.12
      *** /tmp/T0FyaiXL Wed Mar 22 07:26:52 2006
      --- /tmp/T1GyaiXL Wed Mar 22 07:26:52 2006
      ***************
      *** 309,318 ****
              * there is one.
              *
              * @param nanosTimeout the maximum time to wait, in nanoseconds
      ! * @return A value less than or equal to zero if the wait has
      ! * timed out; otherwise an estimate, that
      ! * is strictly less than the <tt>nanosTimeout</tt> argument,
      ! * of the time still remaining when this method returned.
              *
              * @throws InterruptedException if the current thread is interrupted (and
              * interruption of thread suspension is supported).
      --- 309,319 ----
              * there is one.
              *
              * @param nanosTimeout the maximum time to wait, in nanoseconds
      ! * @return An estimate of the <tt>nanosTimeout</tt> value minus
      ! * the time spent waiting upon return from this method. A
      ! * positive value may be used as the argument to a subsequent call
      ! * to this method to finish waiting out the desired time. A value
      ! * less than or equal to zero indicates that no time remains.
              *
              * @throws InterruptedException if the current thread is interrupted (and
              * interruption of thread suspension is supported).

            martin Martin Buchholz
            martin Martin Buchholz
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: