public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: libstdc++/7439: C99 compat: Can't use the name INFINITY in an enum.
Date: Fri, 02 Aug 2002 11:26:00 -0000	[thread overview]
Message-ID: <20020802182602.25781.qmail@sources.redhat.com> (raw)

The following reply was made to PR libstdc++/7439; it has been noted by GNATS.

From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: bkoz@gcc.gnu.org
Cc: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, greyleaf@attbi.com,
   nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Subject: Re: libstdc++/7439: C99 compat: Can't use the name INFINITY in an enum.
Date: 02 Aug 2002 20:18:16 +0200

 bkoz@gcc.gnu.org writes:
 
 | Old Synopsis: Can't use the name INFINITY in an enum.
 | New Synopsis: C99 compat: Can't use the name INFINITY in an enum.
 | 
 | State-Changed-From-To: open->analyzed
 | State-Changed-By: bkoz
 | State-Changed-When: Fri Aug  2 09:52:38 2002
 | State-Changed-Why:
 |     This comes from /usr/include/bits/mathdef.h:
 |     
 |     # define INFINITY	HUGE_VALF
 |     
 |     It looks like INFINITY is a C99 macro. 
 |     
 |     Currently, the plan WRT libstdc++ and C99 macros is undefined. It's also an issue for things like isnan, et. al. It's also a cause for the persistent failure of
 |     
 |     26_numerics/c99_classification_macros_c++.cc
 |     
 |     I don't know what to do, but whatever is done should be consitent with all of these C99'isms.
 
 As part of my current work, I will provide support for infinities in
 numeric_limits<> so that the INFINITY macro become redondant.  Then
 in the compliant C headers, we could #undef them.
 
 I'll post a RFC for a possible strategy with C99 macros.
 
 Thanks,
 
 -- Gaby


             reply	other threads:[~2002-08-02 18:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-02 11:26 Gabriel Dos Reis [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-08-02  9:52 bkoz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020802182602.25781.qmail@sources.redhat.com \
    --to=gdr@integrable-solutions.net \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).