From owner-freebsd-current@FreeBSD.ORG Mon Jul 14 13:33:31 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 4F23937B401 for ; Mon, 14 Jul 2003 13:33:31 -0700 (PDT) Received: from smtpout.mac.com (A17-250-248-88.apple.com [17.250.248.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 94A9943F3F for ; Mon, 14 Jul 2003 13:33:30 -0700 (PDT) (envelope-from leimy2k@mac.com) Received: from webmail01.mac.com (webmail01-en1 [10.13.11.143]) by smtpout.mac.com (Xserve/MantshX 2.0) with ESMTP id h6EKXRkc027255; Mon, 14 Jul 2003 13:33:27 -0700 (PDT) Received: from webmail01 (localhost [127.0.0.1]) by webmail01.mac.com (8.12.2/8.12.2) with ESMTP id h6EKXQ9k014081; Mon, 14 Jul 2003 13:33:26 -0700 (PDT) Message-ID: <5574086.1058214806759.JavaMail.leimy2k@mac.com> Date: Mon, 14 Jul 2003 15:33:26 -0500 From: David Leimbach To: Terry Lambert Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit cc: Craig Rodrigues cc: Alexander Kabaev cc: freebsd-current@freebsd.org Subject: Re: GCC 3.3.1, new warnings with 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: Mon, 14 Jul 2003 20:33:31 -0000 On Monday, July 14, 2003, at 01:33PM, Terry Lambert wrote: >David Leimbach wrote: >> This is a good policy in general, however, one could easily argue that >> what is trying to be determined with signedness and such being >> less-than-compared >> to 0 isn't really a big deal and possibly the only way to implement this >> numeric_limits::digits thing without any type introspection which >> C++ currently >> lacks. >> >> The following would work for example in a template function: > >[ ... ] > True... but I don't think I was talking about a one-shot disabling of the message. I was thinking more about how a compliant C++ compiler can determine the signedness of a datatype without type introspection or type metadata available at compile time. [which seems to be what numeric_limits is all about doesn't it?] Dave >Gcc needs a #pragma to disable specific warnings as a one-shot. > >This was discussed in detail on the GCC mailing list. > >-- Terry > >