| … | |
… | |
| 3 | TODO: should explore PerlIO::via::CoroCede and PerlIO::via::CoroAIO. |
3 | TODO: should explore PerlIO::via::CoroCede and PerlIO::via::CoroAIO. |
| 4 | TODO: maybe implement a default message channel, very much like Erlang's |
4 | TODO: maybe implement a default message channel, very much like Erlang's |
| 5 | actor model (which is cool in a lot of important aspects (failures!), |
5 | actor model (which is cool in a lot of important aspects (failures!), |
| 6 | but very lacking in others (higher level ipc)). |
6 | but very lacking in others (higher level ipc)). |
| 7 | |
7 | |
|
|
8 | 4.6 Sat Apr 26 10:05:14 CEST 2008 |
|
|
9 | - INCOMPATIBLE CHANGE: sub/code attributes are no longer supported |
|
|
10 | by the Coro module. It was a mistake to have it in the first place. |
|
|
11 | - (experimental) support for activestate perl 5.10 (method "w"). |
|
|
12 | - (experimental) support for strawberry perl (method "a"). |
|
|
13 | - coro_sigelem_set did not return a value although it had to, |
|
|
14 | actual impact unknown. |
|
|
15 | |
|
|
16 | 4.51 Mon Apr 14 13:28:27 CEST 2008 |
|
|
17 | - make it compile again on 5.8. |
|
|
18 | |
|
|
19 | 4.50 Thu Apr 10 09:43:17 CEST 2008 |
|
|
20 | - I did it twice! (see 4.49). |
|
|
21 | |
|
|
22 | 4.49 Sun Apr 6 21:23:31 CEST 2008 |
|
|
23 | - grr, instead of compiling the recent changes on 5.10 only they |
|
|
24 | were compiled on 5.8 only. |
|
|
25 | |
|
|
26 | 4.48 Sun Apr 6 20:36:46 CEST 2008 |
| 8 | - allow coroutine switches during eval's under 5.10.x, as it seems |
27 | - allow coroutine switches during eval's under 5.10.x, as it seems |
| 9 | the parser is a per-interpreter option now, so this is safe |
28 | the parser is a per-interpreter option now, so this is safe |
| 10 | (this might fix the odd crashing bug). |
29 | (this might fix the odd crashing bug). |
| 11 | - drop support for 5.9.x versions, they are dead, jim. |
30 | - drop support for 5.9.x versions: they are dead, jim. |
| 12 | |
31 | |
| 13 | 4.47 Sun Apr 6 00:37:52 CEST 2008 |
32 | 4.47 Sun Apr 6 00:37:52 CEST 2008 |
| 14 | - force cctx allocation on API calls: we know we need to force one |
33 | - force cctx allocation on API calls: we know we need to force one |
| 15 | and gcc actually manages to confuse our heuristic nowadays, |
34 | and gcc actually manages to confuse our heuristic nowadays, |
| 16 | leading to crashes and worse. |
35 | leading to crashes and worse. |
