| 23 |
|
implement or inherit from their specifications. |
| 24 |
|
</em> |
| 25 |
|
|
| 26 |
< |
<p> JSR-166 introduces package <tt>java.util.concurrent</tt> |
| 26 |
> |
<p>JSR-166 introduces package <tt>java.util.concurrent</tt> |
| 27 |
|
containing utility classes commonly useful in concurrent |
| 28 |
|
programming. Like package <tt>java.util</tt>, it includes a few small |
| 29 |
|
standardized extensible frameworks, as well as other classes that |
| 30 |
|
provide useful functionality and are otherwise tedious or difficult to |
| 31 |
|
implement. |
| 32 |
|
|
| 33 |
< |
<p>JSR-166 focusses on breadth, providing critical functionality |
| 33 |
> |
<p>JSR-166 focuses on breadth, providing critical functionality |
| 34 |
|
useful across a wide range of concurrent programming styles and |
| 35 |
|
applications, ranging from low-level atomic operations, to |
| 36 |
|
customizable locks and synchronization aids, to various concurrent |
| 60 |
|
class: |
| 61 |
|
<ul> |
| 62 |
|
<li> It now allows per-thread installation of handlers for uncaught |
| 63 |
< |
exceptions. Ths optionally disassociates handlers from ThreadGroups, |
| 63 |
> |
exceptions. This optionally disassociates handlers from ThreadGroups, |
| 64 |
|
which has proven to be too inflexible. (Note that the combination of |
| 65 |
|
features in JSR-166 make ThreadGroups even less likely to be used in |
| 66 |
|
most programs. Perhaps they will eventually be deprecated.) |
| 75 |
|
<tt>InterruptedExceptions</tt>. |
| 76 |
|
<li> The <tt>destroy</tt> method, which has never been implemented, |
| 77 |
|
has finally been deprecated. This is just a spec change, reflecting |
| 78 |
< |
the fact that that the reason it has never been implemented is that |
| 78 |
> |
the fact that the reason it has never been implemented is that |
| 79 |
|
it was undesirable and unworkable. |
| 80 |
|
</ul> |
| 81 |
|
|
