[PEAK] New naming proposal: events.Thread -> events.Task

[Bob Ippolito]

On Feb 5, 2004, at 8:06 PM, Phillip J. Eby wrote:

> ITask -> IProcedure  (generator that defines the work done in a task)
>
> Thread -> Task
>
> ThreadState -> TaskState  (maintains the task's stack of currently 
> executing IProcedures)
>
> threaded -> taskFactory (generator function that creates a task when 
> invoked, becoming the task's current IProcedure)
>
> IThread -> ITask
>
> IThreadState -> ITaskState
>
> ITaskSwitch -> no change
>
>
> Any objections?  The purpose here is for the terminology to be 
> clearer, and avoid "threading" baggage.  It also helps to emphasize 
> that you need a particular kind of "procedure" in order to do 
> co-operative multitasking.
>
> Last, but not least, it points to the fact that there really aren't 
> any "threads", but instead just a bunch of tasks that you keep track 
> of and switch between.

This one gets my vote.. in Stackless, they're actually called tasklets, 
so it makes sense to use similar terminology.

-bob