Revision: 3615 http://trac.macosforge.org/projects/ruby/changeset/3615 Author: ernest.prabhakar@gmail.com Date: 2010-02-24 17:39:54 -0800 (Wed, 24 Feb 2010) Log Message: ----------- Document Dispatch::Source not needing +synchronize+ Modified Paths: -------------- MacRuby/trunk/lib/dispatch/README.rdoc Modified: MacRuby/trunk/lib/dispatch/README.rdoc =================================================================== --- MacRuby/trunk/lib/dispatch/README.rdoc 2010-02-25 01:39:09 UTC (rev 3614) +++ MacRuby/trunk/lib/dispatch/README.rdoc 2010-02-25 01:39:54 UTC (rev 3615) @@ -253,7 +253,7 @@ * Mach ports * Custom application-specific events -When the source “fires,” GCD will schedule the handler on the specific queue if it is not currently running, or -- more importantly -- coalesce pending events if it is. This provides excellent responsiveness without the expense of either polling or binding a thread to the event source. Plus, since the handler is never run more than once at a time, the block doesn’t even need to be reentrant. +When the source “fires,” GCD will schedule the handler on the specific queue if it is not currently running, or -- more importantly -- coalesce pending events if it is. This provides excellent responsiveness without the expense of either polling or binding a thread to the event source. Plus, since the handler is never run more than once at a time, the block doesn’t even need to be reentrant -- and thus you don't need to +synchronize+ any variables that are only used there. === Dispatch::Source.interval
participants (1)
-
source_changes@macosforge.org