bindat(2) and connectat(2) syscalls for review.

Pawel Jakub Dawidek pjd at FreeBSD.org
Sun Feb 17 09:58:12 UTC 2013


On Sun, Feb 17, 2013 at 04:21:00AM +0100, Dag-Erling Smørgrav wrote:
> Pawel Jakub Dawidek <pjd at FreeBSD.org> writes:
> > Dag-Erling Smørgrav <des at des.no> writes:
> > > Jilles Tjoelker <jilles at stack.nl> writes:
> > > > A flag parameter is a good thing; you may not know yet what you will
> > > > need it for.
> > > int bind(int s, const struct sockaddr *addr, socklen_t addrlen);
> > > int connect(int s, const struct sockaddr *name, socklen_t namelen);
> > > Where's the flag argument?
> > The is no flag argument in my patch, but it was proposed by Kostik in
> > the e-mail Jilles replied to.
> 
> That was a rhetorical question...  unless Jilles wants to go through our
> entire code base and add a flag argument to every syscall or library
> function that doesn't already have one, "just in case".

Sorry, I thought you pasted bindat() and connectat() prototypes...

-- 
Pawel Jakub Dawidek                       http://www.wheelsystems.com
FreeBSD committer                         http://www.FreeBSD.org
Am I Evil? Yes, I Am!                     http://tupytaj.pl
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-arch/attachments/20130217/c8757bed/attachment.sig>


More information about the freebsd-arch mailing list