Subject:
|
Re: The BrickOS Task Manager
|
Newsgroups:
|
lugnet.robotics.rcx.legos
|
Date:
|
Tue, 6 Jan 2004 03:49:44 GMT
|
Viewed:
|
3436 times
|
| |
|
|
IIRC the issue was that Task, Process and Thread were all used to
represent the same item/concept in the Kernel code.
After some discussion, it was decided that the word Task would be used
in all cases. This improves readability, etc... (ie. Task Manager)
So, tid_t -> Task ID
// Joe
Ralph Clark wrote:
> tid_t -> thread ID
> pid_t -> process ID
>
> ?
>
> "nanobapt" <nanobapt@wanadoo.fr> wrote in message
> news:3FF95FD4.6080209@wanadoo.fr...
>
> > in version 2.6.1 (I've just download it)
> >
> > extern tid_t execi(int (*code_start) (int, char **), int argc, char
> > **argv, priority_t priority, size_t stack_size);
> >
> > declare in unistd.h !
> >
> > So use the tid_t and not the pid_t ! (like say ROSCO)
> >
> > Does anyone know why thez change pid_t to tid_t ?
> >
> > nanobapt
>
>
>
>
|
|
Message has 1 Reply:
 | | Re: The BrickOS Task Manager
|
| (...) Sorry, I'm still just not getting it at all. I have type errors all over the place trying to pass arguments to my task. Could someone please simply email me or post an example of a program that starts, runs two or more threads, and will (...) (20 years ago, 10-Jan-04, to lugnet.robotics.rcx.legos)
|
Message is in Reply To:
15 Messages in This Thread:
 
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
