[ViewVC] Diff of: cvs/OpenCL/OpenCL.pm

Comparing OpenCL/OpenCL.pm (file contents):
Revision 1.73 by root, Fri May 4 14:56:50 2012 UTC vs.
Revision 1.74 by root, Fri May 4 15:04:51 2012 UTC

 OpenCL can generate a number of (potentially) asynchronous events, for
 example, after compiling a program, to signal a context-related error or,
 perhaps most important, to signal completion of queued jobs (by setting
 callbacks on OpenCL::Event objects).
+The OpenCL module converts all these callbacks into events - you can
+still register callbacks, but they are not executed when your OpenCL
+implementation calls the actual callback, but only later. Therefore, none
+of the limitations of OpenCL callbacks apply to the perl implementation:
+it is perfectly safe to make blocking operations from event callbacks, and
+enqueued operations don't need to be flushed.
 To facilitate this, this module maintains an event queue - each
 time an asynchronous event happens, it is queued, and perl will be
 interrupted. This is implemented via the L<Async::Interrupt> module. In
 addition, this module has L<AnyEvent> support, so it can seamlessly
 integrate itself into many event loops.
-Since this module is a bit hard to understand, here are some case examples:
+Since L<Async::Interrupt> is a bit hard to understand, here are some case examples:
 =head3 Don't use callbacks.
 When your program never uses any callbacks, then there will never be any
 notifications you need to take care of, and therefore no need to worry

-–
+Removed lines
-+
+Added lines
-<
+Changed lines
->
+Changed lines