Added more notes

This commit is contained in:
Justin Ethier 2016-01-03 23:02:11 -05:00
parent d2cbfaf217
commit c32cbdad9a

View file

@ -7,6 +7,8 @@ Phase 6 (gc-dev6) - Multiple mutators (application threads)
Phase 7 (TBD) - Sharing of variables between threads (ideally without limitation, but that might not be realistic) Phase 7 (TBD) - Sharing of variables between threads (ideally without limitation, but that might not be realistic)
TODO: TODO:
- merge everything back to master??? I think it's just about time
- move mutations into local thread data
- multiple mutators, and threading functions/types. probably want this on a new branch, when ready - multiple mutators, and threading functions/types. probably want this on a new branch, when ready
part of this is implementing the beginnings of srfi-18, to create multiple threads, sync them, etc part of this is implementing the beginnings of srfi-18, to create multiple threads, sync them, etc
next steps: next steps:
@ -17,7 +19,11 @@ TODO:
- bring exceptions into local thread data? anything else? - bring exceptions into local thread data? anything else?
also, will probably need to lock shared resources such as I/O... also, will probably need to lock shared resources such as I/O...
- need a legitimate test program that uses mutexes. am worried that when lock calls into a cont, the program will crash because it returns a boolean object, which the runtime does not handle
- user manual
need to document everything, including:
- how to use cyclone (meta files, compiling modules, etc)
- what to be cognizant of when writing threading code. esp, how to deal with stack objects (initiating minor GC's, etc)
DONE: DONE:
- need to cooperate when a mutator is blocked - need to cooperate when a mutator is blocked