FJP.CommonPool and VM shutdown (original) (raw)
Doug Lea dl at cs.oswego.edu
Tue Jan 1 10:11:14 PST 2013
- Previous message: FJP.CommonPool and VM shutdown
- Next message: FJP.CommonPool and VM shutdown
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Oh, just to be extra-clear:
On 01/01/13 11:55, Doug Lea wrote:
Not really. It was always the case that if you wanted to wait out a submitted async FJ task from main() (to any FJP), you had to awaitTermination.
That is, some submitted task that you don't know about and so cannot join.
Only those few people who do this (mainly Martin Buchholz and me, writing test code!) ever had to think about it. Now there is another uncommon case along these lines, with the implicit common pool, but it can now be programmed in exactly the same way.
-Doug
- Previous message: FJP.CommonPool and VM shutdown
- Next message: FJP.CommonPool and VM shutdown
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the lambda-libs-spec-observers mailing list