Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 21 Mar 2000 10:53:30 -0800
From:      bmah@CA.Sandia.GOV (Bruce A. Mah)
To:        Yoshinobu Inoue <shin@nd.net.fujitsu.co.jp>
Cc:        bde@zeta.org.au, nnd@mail.nsk.ru, current@FreeBSD.ORG
Subject:   Re: 'machine/param.h' required for 'sys/socket.h' 
Message-ID:  <200003211853.e2LIrUg87051@nimitz.ca.sandia.gov>
In-Reply-To: <20000322024911Q.shin@nd.net.fujitsu.co.jp> 
References:  <20000322013459L.shin@nd.net.fujitsu.co.jp> <Pine.BSF.4.21.0003220428230.4710-100000@alphplex.bde.org> <20000322024911Q.shin@nd.net.fujitsu.co.jp>

next in thread | previous in thread | raw e-mail | index | archive | help
--==_Exmh_789141986P
Content-Type: text/plain; charset=us-ascii

If memory serves me right, Yoshinobu Inoue wrote:
> > > I feel requesting inclusion of machine/param.h for any apps
> > > which use socket is better. But if there are any other smarter
> > > solution, please let me know and I'll appreciate it much.
> > 
> > <machine/param.h> should never be included by applications since
> > it is an implementation detail.
> > 
> > Specify including <sys/param.h> in apps which use the CMSG*() macros.
> > <sys/socket.h> doesn't depend on <*/param.h> unless these macros are used.
> > Since these macros are undocumented, applications that use them should
> > expect problems :-).
> > 
> > Bruce
> 
> After reading bmah's message, now I am inclined to including
> machine/param.h from sys/socket.h for maximum portability, if
> there is no spec for it, and if all other platforms doing it.

Arrgh.  Now it seems I might need to reverse my position.  I looked
through some code fragments in UNIX Network Programming (Volume 1,
Second Edition, pp. 362-365), and there's some precedent for needing
<sys/param.h> with the CMSG*() macros.

On the other hand, RFC 2292 and draft-ietf-ipngwg-rfc2292bis (the
references I was originally working from) don't mention this requirement
at all; they just say that CMSG*() are defined with <sys/socket.h>.  I'm
slightly confused by now.

I'm going to send off a note to the authors of 
draft-ietf-ipngwg-rfc229bis asking for some clarification.  In the 
meantime, maybe we should hold off on doing any changes.

Bruce.



--==_Exmh_789141986P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 5.0i for non-commercial use
MessageID: 8v9hQWl8rwWL3H+0/R4zKr2stejjn8GI

iQA/AwUBONfFKdjKMXFboFLDEQIF8wCgqspEwzh/iJt8yOjlp7OO3nNtguYAoJNy
PxqIQxugikuNZkB7sJ3YBnUC
=5SBz
-----END PGP SIGNATURE-----

--==_Exmh_789141986P--


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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200003211853.e2LIrUg87051>