From owner-freebsd-arch@FreeBSD.ORG Sun Feb 17 03:21:03 2013 Return-Path: Delivered-To: freebsd-arch@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 9074389D; Sun, 17 Feb 2013 03:21:03 +0000 (UTC) (envelope-from des@des.no) Received: from smtp.des.no (smtp.des.no [194.63.250.102]) by mx1.freebsd.org (Postfix) with ESMTP id 464207C1; Sun, 17 Feb 2013 03:21:02 +0000 (UTC) Received: from ds4.des.no (smtp.des.no [194.63.250.102]) by smtp-int.des.no (Postfix) with ESMTP id AE6EC6992; Sun, 17 Feb 2013 03:21:01 +0000 (UTC) Received: by ds4.des.no (Postfix, from userid 1001) id 61EB8924E; Sun, 17 Feb 2013 04:21:01 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Pawel Jakub Dawidek Subject: Re: bindat(2) and connectat(2) syscalls for review. References: <20130213230354.GC1375@garage.freebsd.pl> <20130213232004.GA2522@kib.kiev.ua> <20130213234030.GD1375@garage.freebsd.pl> <20130214185549.GA36288@stack.nl> <86ip5saqiu.fsf@ds4.des.no> <20130216232039.GD2023@garage.freebsd.pl> Date: Sun, 17 Feb 2013 04:21:00 +0100 In-Reply-To: <20130216232039.GD2023@garage.freebsd.pl> (Pawel Jakub Dawidek's message of "Sun, 17 Feb 2013 00:20:39 +0100") Message-ID: <86y5enaan7.fsf@ds4.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.2 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: Konstantin Belousov , Jilles Tjoelker , freebsd-arch@FreeBSD.org X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Feb 2013 03:21:03 -0000 Pawel Jakub Dawidek writes: > Dag-Erling Sm=C3=B8rgrav writes: > > Jilles Tjoelker 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". DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no