public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: struct msghdr in socket.h is wrong
Date: Mon, 17 Oct 2005 08:44:00 -0000	[thread overview]
Message-ID: <20051017084416.GA11091@calimero.vinschen.de> (raw)
In-Reply-To: <u64rydwtj.fsf@gnu.org>

On Oct 15 22:23, Sam Steingold wrote:
> > * Corinna Vinschen <pbevaan-pltjva@pltjva.pbz> [2005-10-12 22:42:34 +0200]:
> >
> > On Oct 12 15:17, Sam Steingold wrote:
> >> cyswin/socket.h:
> >> 
> >> struct msghdr
> >> {
> >> 	void	*	msg_name;	/* Socket name			*/
> >> 	int		msg_namelen;	/* Length of name		*/
> >> 	struct iovec *	msg_iov;	/* Data blocks			*/
> >> 	int		msg_iovlen;	/* Number of blocks		*/
> >> 	void	*	msg_accrights;	/* Per protocol magic (eg BSD file descriptor passing) */
> >> 	int		msg_accrightslen;	/* Length of rights list */
> >> };
> >
> > This is the so called "older" implementation of struct msghdr as
> > defined up to 4.2BSD.  Since it's quite useless so far and since
> 
> I am not sure I quite understand what you mean by useless.
> is cygwin implementation somehow deficient?
> 
sendmsg and recvmsg don't utilize the msg_accrights/msg_accrightslen member.

> > applications using this structure should accomodate the old
> > implementation anyway, I don't see a good reason to change this right
> > now.
> 
> the only reason applications have to accommodate the old implementation
> is that some unixes still stick with it.

So, from a portability perspective...

> if you switch to the posix msghdr, I, for one, would not have to
> accomodate the old implementation.

I won't change it now.  I'll change it at one point when there's some
functionality.

Hint: Applications using only the first four members of this structure
will be binary compatible...


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat, Inc.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

  reply	other threads:[~2005-10-17  8:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-12 19:18 Sam Steingold
2005-10-12 20:42 ` Corinna Vinschen
2005-10-16  2:24   ` Sam Steingold
2005-10-17  8:44     ` Corinna Vinschen [this message]
2005-10-17 21:34       ` Corinna Vinschen
2005-10-21 20:19         ` Sam Steingold
2005-10-22  9:07           ` Corinna Vinschen
2005-10-22 17:02             ` Corinna Vinschen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20051017084416.GA11091@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).