BEGIN LICENSE BLOCK *****
Version: EPL 1.0/GPL 2.0/LGPL 2.1
The contents of this file are subject to the Eclipse Public
License Version 1.0 (the "License"); you may not use this file
except in compliance with the License. You may obtain a copy of
the License at http://www.eclipse.org/legal/epl-v10.html
Software distributed under the License is distributed on an "AS
IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or
implied. See the License for the specific language governing
rights and limitations under the License.
Copyright (C) 2007 Charles O Nutter <firstname.lastname@example.org>
Alternatively, the contents of this file may be used under the terms of
either of the GNU General Public License Version 2 or later (the "GPL"),
or the GNU Lesser General Public License Version 2.1 or later (the "LGPL"),
in which case the provisions of the GPL or the LGPL are applicable instead
of those above. If you wish to allow use of your version of this file only
under the terms of either the GPL or the LGPL, and not to allow others to
use your version of this file under the terms of the EPL, indicate your
decision by deleting the provisions above and replace them with the notice
and other provisions required by the GPL or the LGPL. If you do not delete
the provisions above, a recipient may use your version of this file under
the terms of any one of the EPL, the GPL or the LGPL.
END LICENSE BLOCK ***
Starting a new thread in terms of a thread pool is just submitting it as
a job to the pool.
In order to do a thread interrupt, we need to get the actual thread, stored
in the RubyRunnable instance and tell it to interrupt. Future does not
provide a mechanism for passing an interrupt to the thread running it.
If the runnable is not being executed by a thread (not yet, or already
done) do nothing.
If the future has not yet run and or is running and not yet complete.
We defined "alive" for a FutureThread to be the following:
The Runnable has not yet been submitted to the Executor. This is equivalent
to a Ruby thread that has not yet been scheduled to run. Because Ruby
considered a thread alive immediately, a FutureThread with no Future yet
is still considered alive, because it will eventually be submitted.
The Runnable has been submitted to the Executor but no Future has
been returned yet. There's a bit of a race here if we expect future to
not be null, since the runnable could be submitted to the Executor and
complete execution before the future is ever assigned. This manifested
as Thread.current.status from within a thread coming up as false...
because isAlive returned false if the future was still null.
The Runnable has been submitted to the Executor, the Future has
been assigned, but the Future is not "done" yet. The thread is running,
and we report it is alive.
All other cases are considered "not alive" and we return fals here.
We check for zero millis here because Future appears to wait for zero if
you pass it zero, where Thread behavior is to wait forever.
We also catch and swallow CancellationException because it means the Future
was cancelled before it ran, and is therefore as done as it will ever be.
The current priority of the thread associated with this future.
- the current priority of the thread in which we this is running
Set the priority of the thread associated with this future.
priority the new priority