Date: Mon, 17 Feb 1997 09:09:51 -0700 From: Warner Losh <imp@village.org> To: hackers@freebsd.org Subject: Luke Mewburn: const-ness of select() timeout arg Message-ID: <E0vwVdY-0007Jo-00@rover.village.org>
next in thread | raw e-mail | index | archive | help
Saw this in netbsd-kern. Just thought I'd pass it along here. I've been telling folks in Linux for 4 years that the timeval is const :-)... Warner ------- Forwarded Message Message-ID: <199702162338.KAA11206@coola.off.connect.com.au> X-Authentication-Warning: coola.off.connect.com.au: lukem owned process doing -bs To: tech-kern@NetBSD.ORG Subject: const-ness of select() timeout arg Date: Mon, 17 Feb 1997 10:38:41 +1100 From: Luke Mewburn <lukem@connect.com.au> Sender: tech-kern-owner@NetBSD.ORG Precedence: list Delivered-To: tech-kern@NetBSD.ORG I saw this on USENET, and thought it might be relevant. It is about POSIX 1.g, and its definition of select() to have a "const" timeout arg. I think I read on one of our mailing lists that NetBSD doesn't depend upon a non-const arg, however our Linux emulation may. In any case, something that should be investigated? === > From: rstevens@noao.edu (W. Richard Stevens) > Newsgroups: comp.unix.programmer > Subject: Re: select call timeout argument > Date: 13 Feb 1997 13:57:50 GMT > Organization: National Optical Astronomy Observatories, Tucson, AZ, USA > Lines: 5 Posix.1g, which is standardizing select() and poll(), add the "const" qualifier to the "struct timeval *". So any system that does update this structure today, will have to change. === ------- End of Forwarded Message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E0vwVdY-0007Jo-00>