From owner-freebsd-questions Fri Jul 3 09:40:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA19605 for freebsd-questions-outgoing; Fri, 3 Jul 1998 09:40:52 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from mail.camalott.com (root@mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA19600 for ; Fri, 3 Jul 1998 09:40:50 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-113.camalott.com [208.229.74.113]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id LAA19853; Fri, 3 Jul 1998 11:41:03 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id LAA10987; Fri, 3 Jul 1998 11:41:02 -0500 (CDT) (envelope-from joelh) Date: Fri, 3 Jul 1998 11:41:02 -0500 (CDT) Message-Id: <199807031641.LAA10987@detlev.UUCP> To: freebsd-questions@FreeBSD.ORG Subject: Dynamic scatter / gather operations From: Joel Ray Holveck Reply-to: joelh@gnu.org Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is it possible / portable / sane for a readv to affect its own iov? That is, something like the following: struct iovec iov[2]; char string[MAXLEN]; iov[0].iov_len = sizeof(iov[1].iov_len); iov[0].iov_base = &(iov[1].iov_len); iov[1].iov_base = string; readv(fd, iov, 2); Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message