diff options
author | pixel <pixel> | 2003-09-06 13:48:16 +0000 |
---|---|---|
committer | pixel <pixel> | 2003-09-06 13:48:16 +0000 |
commit | 98f47b848b9917cdecbe9c0ba27e339cb55f0cf8 (patch) | |
tree | 64dff0406738d066445c95e24277816ce122d5c5 | |
parent | d4a8ce20018536ca26564d5dc92c1c051316df4f (diff) |
Typos
-rw-r--r-- | doc/API | 8 |
1 files changed, 4 insertions, 4 deletions
@@ -19,9 +19,9 @@ pipe fork exit -I did wrote some little and stupid memory functions. Maybe I'll later use +I did write some little and stupid memory functions. Maybe I'll later use dlmalloc or something like this. The other function will throw an exception -if something went wrong. +if something goes wrong. If you can't write an inner-class function that has to allocate memory, use the x* functions: @@ -558,7 +558,7 @@ the task will be awoken if something bad happends to the handle. When a watch over a Handle occures, the watch is removed, unless W4_STICKY. A task can do anythings it wants, especially causing a GeneralException. Then it -will ended by the TaskMan, like if it did returned TASK_DONE. +will ended by the TaskMan, like if it did return TASK_DONE. Well I hoped I was enough clear. If not, read the source code of the following classes: @@ -567,7 +567,7 @@ classes: Class CopyJob: ------------- -This task takes four parameters as creator: +This task takes four parameters as constructor: CopyJob(Handle * s, Handle * d, ssize_t max = -1, bool ds = false); The task will copy the handle s to the handle d. If max != -1 then it will copy |