This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "aesop Repository". The branch, master has been updated via f6ce31fb24d5ea9db0ebb21095c41061009337f2 (commit) from a3ac9a69b1bb6965f2727af7deef3175877c7548 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit f6ce31fb24d5ea9db0ebb21095c41061009337f2 Author: Kevin Harms <[email protected]> Date: Tue Feb 28 14:43:18 2012 -0600 Minor edits to aug_language.txt ----------------------------------------------------------------------- Summary of changes: doc/aug_language.txt | 8 ++++---- 1 files changed, 4 insertions(+), 4 deletions(-) Diff of changes: diff --git a/doc/aug_language.txt b/doc/aug_language.txt index 5c7a230..a9c1d0c 100644 --- a/doc/aug_language.txt +++ b/doc/aug_language.txt @@ -63,7 +63,7 @@ execution, and are used by aesop to introduce concurrency to the C language. -The `__blocking` qualifyier +The `__blocking` qualifier ~~~~~~~~~~~~~~~~~~~~~~~~~~~ All blocking functions must be marked as such. Below is an example of a @@ -138,7 +138,7 @@ execution to code that is ready to execute while waiting for the external event to occur. For example, a function reading data from the network or a disk will typically -be blocking, since the function I/O bound. If the function is blocking, as +be blocking, since the function is I/O bound. If the function is blocking, as soon as the processor core would become idle, execution can continue elsewhere. If the function is not blocking, the processor core would become idle until the read completes. @@ -285,7 +285,7 @@ In the example above, each pbranch will get a private copy of the loop variable `i`. Since the next iteration of the loop does not depend on the completion of the pbranch, `pprivate` is required here to prevent changes to the value of `i` in a pbranch while the branch is still executing. -In this case, `pprivate` required, as manually assigning `i` to a private copy +In this case, `pprivate` is required, as manually assigning `i` to a private copy would be prone to a race condition. @@ -360,7 +360,7 @@ Lonely pbranches ~~~~~~~~~~~~~~~~~ It is possible to use a `pbranch` outside of `pwait`. In this case, the -pbranch executes as normal but it not possible to wait for the branch +pbranch executes as normal but it not possible to wait for the branch to complete. hooks/post-receive -- aesop Repository