From owner-freebsd-current@FreeBSD.ORG Wed Dec 31 06:18:33 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1497016A4CE for ; Wed, 31 Dec 2003 06:18:33 -0800 (PST) Received: from fafoe.narf.at (chello212186121237.14.vie.surfer.at [212.186.121.237]) by mx1.FreeBSD.org (Postfix) with ESMTP id DBA5B43D2F for ; Wed, 31 Dec 2003 06:18:31 -0800 (PST) (envelope-from stefan@fafoe.narf.at) Received: from wombat.fafoe.narf.at (wombat.fafoe.narf.at [192.168.1.42]) by fafoe.narf.at (Postfix) with ESMTP id 8108A40EE; Wed, 31 Dec 2003 15:18:27 +0100 (CET) Received: by wombat.fafoe.narf.at (Postfix, from userid 1001) id EBEA11AC; Wed, 31 Dec 2003 15:18:25 +0100 (CET) Date: Wed, 31 Dec 2003 15:18:25 +0100 From: Stefan Farfeleder To: Max Laier Message-ID: <20031231141546.GC595@wombat.fafoe.narf.at> Mail-Followup-To: Max Laier , Mark Huizer , current@freebsd.org References: <20031231130800.GB59239@eeyore.local.dohd.org> <200312311421.25383.max@love2party.net> <20031231132651.GC59239@eeyore.local.dohd.org> <200312311441.23719.max@love2party.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200312311441.23719.max@love2party.net> User-Agent: Mutt/1.5.5.1i cc: current@freebsd.org Subject: Re: kern.osreldate and EAI_NODATA deprecation X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Dec 2003 14:18:33 -0000 On Wed, Dec 31, 2003 at 02:41:23PM +0100, Max Laier wrote: > On Wednesday 31 December 2003 14:26, Mark Huizer wrote: > > > > Well, that's tougher, since EAI_NODATA is defined (it's defined to be > > EAI_NODATA). > > Hmm... > > would this work? I'm not too 100% secure about preprocessing stuff. > > If this should work, I could try to get it included in the normal kaffe > > tree. > > > > #if defined(EAI_NODATA) && EAI_NODATA != EAI_NONAME > > ... > > #endif > > Other question, does it hurt you that EAI_NODATA == EAI_NONAME? I'd not think > so ... so why borther?! But yes, the syntax is okay ... consider extra > parentheses for the second expression. Eg. it does matter if both macros occur in case labels of a switch statement. Regards, Stefan Farfeleder