From owner-freebsd-arch Sat Jan 27 15:50:14 2001 Delivered-To: freebsd-arch@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id EC8A237B400 for ; Sat, 27 Jan 2001 15:49:56 -0800 (PST) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.0/8.9.3) with ESMTP id f0RNnrO31566; Sat, 27 Jan 2001 16:49:53 -0700 (MST) (envelope-from gibbs@scsiguy.com) Message-Id: <200101272349.f0RNnrO31566@aslan.scsiguy.com> To: Dag-Erling Smorgrav Cc: freebsd-arch@FreeBSD.ORG Subject: Re: Proposed change to sbuf semantics In-Reply-To: Your message of "28 Jan 2001 00:06:37 +0100." Date: Sat, 27 Jan 2001 16:49:53 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> In otherwords, I'd like to be able to test if an >> sbuf has been written to before it has been finalized >> so you can do things like: > >Well, you can use sbuf_len() for that. It returns 0 if the sbuf is >empty, -1 if it overflowed, and the length of its contents otherwise. I thought that sbuf_len() required a finalized buffer. Did you change this in your patches? -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message