From owner-freebsd-hackers  Thu Oct 26 10:15:10 2000
Delivered-To: freebsd-hackers@freebsd.org
Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147])
	by hub.freebsd.org (Postfix) with ESMTP id B729237B4CF
	for <freebsd-hackers@FreeBSD.ORG>; Thu, 26 Oct 2000 10:15:05 -0700 (PDT)
Received: from critter (localhost [127.0.0.1])
	by critter.freebsd.dk (8.11.1/8.9.3) with ESMTP id e9QHF1N00900;
	Thu, 26 Oct 2000 19:15:01 +0200 (CEST)
	(envelope-from phk@critter.freebsd.dk)
To: Bob Willcox <bob@immure.com>
Cc: hackers list <freebsd-hackers@FreeBSD.ORG>
Subject: Re: STAILQ_LAST -- what should it return? 
In-Reply-To: Your message of "Thu, 26 Oct 2000 12:12:43 CDT."
             <20001026121243.A38987@luke.immure.com> 
Date: Thu, 26 Oct 2000 19:15:01 +0200
Message-ID: <898.972580501@critter>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <20001026121243.A38987@luke.immure.com>, Bob Willcox writes:

>To follow-up my own question, it appears that the STAILQ_LAST macro has
>been changed (fixed) in -current to return the address of the last entry
>(or NULL if the list is empty).

Please don't MFS sys/queue.h from -current.  It bogusly #includes
<struct.h>.  I have a patch which is in the finishing stages of
brucification right now.


>> #define STAILQ_LAST(head)       (*(head)->stqh_last)
>> 

--
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message