| … | |
… | |
| 48 | } |
48 | } |
| 49 | |
49 | |
| 50 | if ($iface) { |
50 | if ($iface) { |
| 51 | print <<EOF; |
51 | print <<EOF; |
| 52 | |
52 | |
| 53 | Coro has the option of using two different ways to implement coroutines |
53 | Coro can use various ways to implement coroutines at the C level: |
| 54 | at the C level: |
|
|
| 55 | |
54 | |
| 56 | u The unix ucontext functions are newer and not implemented in older |
55 | u The unix ucontext functions are newer and not implemented in older |
| 57 | unices (or broken libc's like glibc-2.2.2 and below). They allow very |
56 | unices (or broken libc's like glibc-2.2.2 and below). They allow very |
| 58 | fast coroutine creation and fast switching, and, most importantly, are |
57 | fast coroutine creation and fast switching, and, most importantly, are |
| 59 | very stable. |
58 | very stable. |
| … | |
… | |
| 68 | l Older GNU/Linux systems (glibc-2.1 and below) need this hack. Since it is |
67 | l Older GNU/Linux systems (glibc-2.1 and below) need this hack. Since it is |
| 69 | very linux-specific it is also quite fast for newer versions; when it |
68 | very linux-specific it is also quite fast for newer versions; when it |
| 70 | works, that is... |
69 | works, that is... |
| 71 | |
70 | |
| 72 | i IRIX. For some reason, SGI really does not like to follow the unix |
71 | i IRIX. For some reason, SGI really does not like to follow the unix |
| 73 | standard (does that surprise you?), so this technique should be fast |
72 | standard (does that surprise you?), so this workaround might be needed |
| 74 | and safe (although s and u should also work now). |
73 | (it's fast), although s and u should also work now. |
| 75 | |
74 | |
| 76 | EOF |
75 | EOF |
| 77 | |
76 | |
| 78 | retry: |
77 | retry: |
| 79 | print "Use which implementation,\n", |
78 | print "Use which implementation,\n", |
