[concurrency-interest] [Javamemorymodel-discussion] Fences.keepAlive

christopher marshall oxbow_lakes at hotmail.com
Wed Jan 21 11:16:29 EST 2009




> Date: Wed, 21 Jan 2009 10:33:48 -0500
> From: dl at cs.oswego.edu
>
> That's the main usability bug with any kind of fence method.
> Fences separate other accesses, which is especially non-intuitive
> in the common case that you cannot see those accesses locally in
> program source. And worse here in that the accesses in question
> surround reachability analysis by GC. And I can't think of
> naming conventions like the pre/post scheme used with other fence
> methods that make sense here. But further suggestions are still welcome.
> 
> "releaseHere" seems out because it mis-implies a directive to
> gc/finalize.
> 

As we're on the subject of fences, how about "enGuarde"


_________________________________________________________________
Cut through the jargon: find a PC for your needs.
http://clk.atdmt.com/UKM/go/130777504/direct/01/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://cs.oswego.edu/pipermail/concurrency-interest/attachments/20090121/1ec21f09/attachment.html>


More information about the Concurrency-interest mailing list