LIST_NEXT()

2001-07-06 Thread Evan Sarmiento
on queue and looked at the proc structure. Here's the code: int prfw_setflags(p, uap) struct proc *p; struct prfw_setflags_args *uap; { ... if (uap-id) { while (uap-id != p-p_pid) LIST_NEXT(p, p_list); } ... } Thanks a lot. Evan Sarmiento To Unsubscribe: send mail to [EMAIL PROTECTED

Re: LIST_NEXT()

2001-07-06 Thread Peter Pentchev
: statement with mo effect What am I doing wrong? I've read the manpages on queue and looked at the proc structure. Here's the code: int prfw_setflags(p, uap) struct proc *p; struct prfw_setflags_args *uap; { ... if (uap-id) { while (uap-id != p-p_pid) LIST_NEXT(p, p_list); } Well, first

Re: LIST_NEXT()

2001-07-06 Thread Eugene L. Vorokov
the manpages on queue and looked at the proc structure. Here's the code: int prfw_setflags(p, uap) struct proc *p; struct prfw_setflags_args *uap; { ... if (uap-id) { while (uap-id != p-p_pid) LIST_NEXT(p, p_list); } ... } The proper way would be: p = LIST_NEXT(p, p_list); Regards

Re: LIST_NEXT()

2001-07-06 Thread John Baldwin
) LIST_NEXT(p, p_list); } Well, first, you're using LIST_NEXT(), not SLIST_NEXT() :) Second, none of the *_NEXT() queue.h macros modify their parameters; they just return a pointer to the next element. So, just try: p = LIST_NEXT(p, p_list); ..and you'll be just fine. However, you