From stdcxx-dev-return-3197-apmail-incubator-stdcxx-dev-archive=incubator.apache.org@incubator.apache.org Wed Apr 11 18:11:54 2007 Return-Path: Delivered-To: apmail-incubator-stdcxx-dev-archive@www.apache.org Received: (qmail 35657 invoked from network); 11 Apr 2007 18:11:53 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 11 Apr 2007 18:11:53 -0000 Received: (qmail 94601 invoked by uid 500); 11 Apr 2007 18:11:59 -0000 Delivered-To: apmail-incubator-stdcxx-dev-archive@incubator.apache.org Received: (qmail 94575 invoked by uid 500); 11 Apr 2007 18:11:59 -0000 Mailing-List: contact stdcxx-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: stdcxx-dev@incubator.apache.org Delivered-To: mailing list stdcxx-dev@incubator.apache.org Received: (qmail 94563 invoked by uid 99); 11 Apr 2007 18:11:59 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Apr 2007 11:11:59 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED,UPPERCASE_25_50 X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Apr 2007 11:11:52 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 5322E71406F for ; Wed, 11 Apr 2007 11:11:32 -0700 (PDT) Message-ID: <15457814.1176315092315.JavaMail.jira@brutus> Date: Wed, 11 Apr 2007 11:11:32 -0700 (PDT) From: "Eric Lemings (JIRA)" To: stdcxx-dev@incubator.apache.org Subject: [jira] Created: (STDCXX-395) Make _RWSTD_WCHAR_T_MIN/MAX names consistent with other *_MIN/MAX names. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Make _RWSTD_WCHAR_T_MIN/MAX names consistent with other *_MIN/MAX names. ------------------------------------------------------------------------ Key: STDCXX-395 URL: https://issues.apache.org/jira/browse/STDCXX-395 Project: C++ Standard Library Issue Type: Improvement Components: Configuration Affects Versions: 4.1.3 Reporter: Eric Lemings Priority: Minor Fix For: 4.1.4 There are numerous MIN/MAX variables defined during configuration. #define _RWSTD_DBL_MAX 1.7976931348623157e+308 #define _RWSTD_FLT_MAX 3.40282347e+38F #define _RWSTD_LDBL_MAX 1.18973149535723176502e+4932L #define _RWSTD_BOOL_MAX !0 #define _RWSTD_CHAR_MAX '\x7f' #define _RWSTD_CHAR_MIN (-_RWSTD_CHAR_MAX - 1) #define _RWSTD_SCHAR_MAX 0x7f #define _RWSTD_SCHAR_MIN (-_RWSTD_SCHAR_MAX - 1) #define _RWSTD_UCHAR_MAX 0xffU #define _RWSTD_SHRT_MAX 0x7fff #define _RWSTD_SHRT_MIN (-_RWSTD_SHRT_MAX - 1) #define _RWSTD_USHRT_MAX 0xffffU #define _RWSTD_INT_MAX 0x7fffffff #define _RWSTD_INT_MIN (-_RWSTD_INT_MAX - 1) #define _RWSTD_UINT_MAX 0xffffffffU #define _RWSTD_LONG_MAX 0x7fffffffffffffffL #define _RWSTD_LONG_MIN (-_RWSTD_LONG_MAX - 1L) #define _RWSTD_ULONG_MAX 0xffffffffffffffffUL #define _RWSTD_LLONG_MAX 0x7fffffffffffffffLL #define _RWSTD_LLONG_MIN (-_RWSTD_LLONG_MAX - 1LL) #define _RWSTD_ULLONG_MAX 0xffffffffffffffffULL #define _RWSTD_WCHAR_T_MAX 0x7fffffff #define _RWSTD_WCHAR_T_MIN (-_RWSTD_WCHAR_T_MAX - 1) #define _RWSTD_MB_LEN_MAX 16 /* libc value */ #define _RWSTD_LC_MAX _RWSTD_LC_IDENTIFICATION #define _RWSTD_SIZE_MAX _RWSTD_ULONG_MAX #define _RWSTD_PTRDIFF_MAX _RWSTD_LONG_MAX #define _RWSTD_RAND_MAX 2147483647 #define _RWSTD_FOPEN_MAX 16 #define _RWSTD_FILENAME_MAX 4096 #define _RWSTD_TMP_MAX 238328 #define _RWSTD_SIG_ATOMIC_MAX _RWSTD_INT_MAX #define _RWSTD_WINT_MAX _RWSTD_UINT_MAX Several of the types covered by these variables use the C naming convention by adding "_t" to the type name (e.g. sig_atomic_t, wint_t, ptrdiff_t) but only _RWSTD_WCHAR_T_MIN/MAX has this suffix in the variable name itself. Request making this variable name consistent with the others. (Why? It makes GNU Automake build support that I'm working on much simpler.) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.