Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
S
shrapnel
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
shrapnel
Commits
b60ba7d9
Commit
b60ba7d9
authored
Dec 07, 2011
by
Sam Rushing
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Commentary on the (slight) misuse of the word 'coro'.
parent
58c996cc
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
8 additions
and
0 deletions
+8
-0
README.rst
README.rst
+8
-0
No files found.
README.rst
View file @
b60ba7d9
...
...
@@ -31,6 +31,14 @@ technique. Written completely in Pyrex. Should remove all
restrictions on coroutine switching, and easily allow for complex
extensions written in C or Pyrex.
Calling Shrapnel a 'coroutine' package is somewhat misleading. Shrapnel
does not provide a 'coroutine' feature. Rather, it *uses* coroutines
to implement a cooperative threading system. You can use it to solve
similar problems, but at a higher level; e.g. use a fifo to pass values
from one thread to another. The package has historically been called
'coro' at IronPort, and you will see the terms 'coro' and 'thread' used
interchangeably in the documentation and source.
Design
======
Shrapnel's overall design is very similar to the previous coro
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment