public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Oleg Krivosheev <kriol@fnal.gov>
To: jbuck@synopsys.com (Joe Buck)
Cc: egcs@cygnus.com
Subject: Re: Cannot build libg++ on Solaris 2.5
Date: Fri, 05 Sep 1997 10:03:00 -0000	[thread overview]
Message-ID: <199709051702.MAA05691@drabble.fnal.gov> (raw)
In-Reply-To: <199709051551.IAA09521@atrus.synopsys.com>

Hi,

> 
> 
> > >>>>> Paul Eggert <eggert@twinsun.com> writes:
> > 
> > > It's necessary to rename `exception' to `__math_exception' until G++
> > > gets fixed.
> > 
> > "fixed"?
> 
> Jason's question is right on the mark.  When g++ is "fixed" to have
> namespaces, the exception class will be in the std namespace.  But guess
> what?  The <math.h> stuff is also supposed to be in the namespace.
> `exception' has to be renamed for C++, period.  That's not going to
> change.


any non-ISO C (89 and then 9X) venfor specific stuff 
should be out of namespace std, IMHO. There should be
no problem.

regards

OK

           reply	other threads:[~1997-09-05 10:03 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <199709051551.IAA09521@atrus.synopsys.com>]

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=199709051702.MAA05691@drabble.fnal.gov \
    --to=kriol@fnal.gov \
    --cc=egcs@cygnus.com \
    --cc=jbuck@synopsys.com \
    /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).