Re: Updated I18N proposal
Nicolas Williams <Nicolas.Williams@sun.com> Thu, 11 May 2006 21:05 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FeIM1-00047O-Ml; Thu, 11 May 2006 17:05:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FeIM0-00046z-2j for kitten@ietf.org; Thu, 11 May 2006 17:05:48 -0400
Received: from brmea-mail-1.sun.com ([192.18.98.31]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FeILy-0006Xq-LE for kitten@ietf.org; Thu, 11 May 2006 17:05:48 -0400
Received: from centralmail3brm.Central.Sun.COM ([129.147.62.199]) by brmea-mail-1.sun.com (8.12.10/8.12.9) with ESMTP id k4BL5kSX027004 for <kitten@ietf.org>; Thu, 11 May 2006 15:05:46 -0600 (MDT)
Received: from binky.Central.Sun.COM (binky.Central.Sun.COM [129.153.128.104]) by centralmail3brm.Central.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL, v2.2) with ESMTP id k4BL5Ief004567 for <kitten@ietf.org>; Thu, 11 May 2006 15:05:19 -0600 (MDT)
Received: from binky.Central.Sun.COM (localhost [127.0.0.1]) by binky.Central.Sun.COM (8.13.3+Sun/8.13.3) with ESMTP id k4BL5j7B001260; Thu, 11 May 2006 16:05:45 -0500 (CDT)
Received: (from nw141292@localhost) by binky.Central.Sun.COM (8.13.3+Sun/8.13.3/Submit) id k4BL5iXh001259; Thu, 11 May 2006 16:05:44 -0500 (CDT)
Date: Thu, 11 May 2006 16:05:44 -0500
From: Nicolas Williams <Nicolas.Williams@sun.com>
To: Jeffrey Hutzelman <jhutz@cmu.edu>
Message-ID: <20060511210544.GA1120@binky.Central.Sun.COM>
Mail-Followup-To: Jeffrey Hutzelman <jhutz@cmu.edu>, Jeffrey Altman <jaltman@columbia.edu>, kitten@ietf.org
References: <F2F0846B87E0A8DF248DE039@sirius.fac.cs.cmu.edu> <200605111958.VAA24539@uw1048.wdf.sap.corp> <20060511200814.GF950@binky.Central.Sun.COM> <DC1DCC3C5EFBD9138704DEB6@sirius.fac.cs.cmu.edu> <20060511203147.GA1091@binky.Central.Sun.COM> <44639F69.2030004@columbia.edu> <44B2E5D054169C72DDCDC159@sirius.fac.cs.cmu.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <44B2E5D054169C72DDCDC159@sirius.fac.cs.cmu.edu>
User-Agent: Mutt/1.5.7i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: kitten@ietf.org
Subject: Re: Updated I18N proposal
X-BeenThere: kitten@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Common Authentication Technologies - Next Generation <kitten.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/kitten>, <mailto:kitten-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/kitten>
List-Post: <mailto:kitten@lists.ietf.org>
List-Help: <mailto:kitten-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/kitten>, <mailto:kitten-request@lists.ietf.org?subject=subscribe>
Errors-To: kitten-bounces@lists.ietf.org
On Thu, May 11, 2006 at 04:56:14PM -0400, Jeffrey Hutzelman wrote: > Right, and my point is that "compile time detection" cannot consist of > compiling and running a test program that uses the run-time detection to > tell you if the feature is available, because that doesn't work in > cross-compile environments. > > It turns out that the art of build-time feature detection is fairly well > understood, at least in the UNIX/C world, and not breaking it is nice. It > turns out that tests that check for existence of a type, function, > preprocessor symbol, etc are fairly easy to do. Tests that check the value > of a preprocessor symbol are a bit harder, and tests that require that you > _call_ a function and check its behavior or return value are very poor. I see this point, but C code that would use functions that may optionally do nothing and return errors SHOULD always do run-time detection of this and SHOULD NOT rely on compile-time detection of such features. Again, I'm not remotely opposed to have pre-processor defines for compile-time detection of features. Nico -- _______________________________________________ Kitten mailing list Kitten@lists.ietf.org https://www1.ietf.org/mailman/listinfo/kitten
- Re: Updated I18N proposal Martin Rex
- Re: Updated I18N proposal Ken Hornstein
- Updated I18N proposal Nicolas Williams
- Re: Updated I18N proposal Jeffrey Hutzelman
- Re: Updated I18N proposal Michael B Allen
- Re: Updated I18N proposal Nicolas Williams
- Re: Updated I18N proposal Martin Rex
- Re: Updated I18N proposal Michael B Allen
- Re: Updated I18N proposal Nicolas Williams
- Re: Updated I18N proposal Jeffrey Altman
- Re: Updated I18N proposal Nicolas Williams
- Re: Updated I18N proposal Michael B Allen
- Re: Updated I18N proposal Nicolas Williams
- Re: Updated I18N proposal Martin Rex
- Re: Updated I18N proposal Nicolas Williams
- Re: Updated I18N proposal Ken Raeburn
- Re: Updated I18N proposal Jeffrey Altman
- Re: Updated I18N proposal Jeffrey Hutzelman
- Re: Updated I18N proposal Martin Rex
- Re: Updated I18N proposal Nicolas Williams
- Re: Updated I18N proposal Jeffrey Hutzelman
- Re: Updated I18N proposal Nicolas Williams
- Re: Updated I18N proposal Martin Rex
- Re: Updated I18N proposal Nicolas Williams
- Re: Updated I18N proposal Nicolas Williams
- Re: Updated I18N proposal Jeffrey Altman
- Re: Updated I18N proposal Nicolas Williams
- Re: Updated I18N proposal Jeffrey Hutzelman
- Re: Updated I18N proposal Nicolas Williams
- Re: Updated I18N proposal Jeffrey Hutzelman
- Re: Updated I18N proposal Jeffrey Hutzelman
- Re: Updated I18N proposal Nicolas Williams
- Re: Updated I18N proposal Jeffrey Hutzelman
- Re: Updated I18N proposal Martin Rex
- Re: Updated I18N proposal Nicolas Williams
- Re: Updated I18N proposal Jeffrey Hutzelman
- Re: Updated I18N proposal Ken Raeburn
- Re: Updated I18N proposal Nicolas Williams
- Re: Updated I18N proposal Jeffrey Hutzelman
- Re: Updated I18N proposal Jeffrey Altman
- Re: Updated I18N proposal Simon Josefsson
- Re: Updated I18N proposal Nicolas Williams