public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Grafe, Christine" <Christine.Grafe@airbus.dasa.de>
To: "'gcc@gcc.gnu.org'" <gcc@gcc.gnu.org>
Subject: C++ Compiler
Date: Thu, 30 Sep 1999 18:02:00 -0000	[thread overview]
Message-ID: <C38EC5EA58E6D111AA690001FA7EEEC9112617@s02mks6.ham.airbus.dasa.de> (raw)
Message-ID: <19990930180200.NA68P6nxopdUNYBr-7_XVO1PYljfRUFm2SHDDRLofYw@z> (raw)

Dear Compiler-specialists,

after some years doing nothing with gnu compilers I want to start to use a
gnu c++-compiler again. My problem I have forgotten about all my experiences
with them and it seems several things have changed. The name has changed
from gcc to egcs but there are still gcc releases.  

It would be very nice if someone could help to pick the right compiler for
my tasks. I want to compile some middle size c++-code programs and I want to
include the Rogue Wave h++ functions. I know from RogueWave itself that
beginning from gcc 2.8  the compiler doesn't find big problems with the h++
code anymore. 
Is anyone there to tell me about Rogue Wave h++ and the egcs compiler or the
gcc2.95 or gcc 2.95.1?

Thanks for your help in advance.
Best regards, Christine

             reply	other threads:[~1999-09-30 18:02 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-08  0:04 Grafe, Christine [this message]
1999-09-08  0:39 ` Martin v. Loewis
1999-09-08  9:23   ` Joe Buck
1999-09-30 18:02     ` Joe Buck
1999-09-30 18:02   ` Martin v. Loewis
1999-09-30 18:02 ` Grafe, Christine
  -- strict thread matches above, loose matches on Subject: below --
2004-12-09 17:57 C++ compiler Stan Gosselin
2004-12-09 18:03 ` Nathan Sidwell
2002-12-23  6:15 C compiler Teekayu
2002-12-23  8:13 ` Andrea 'fwyzard' Bocci
2001-11-07 12:19 kabir.patel
2001-11-02  7:57 Brian Abbott
2001-11-02  9:38 ` Chip Cuntz
2001-11-02  7:20 mike stump
2001-11-01 15:36 kabir.patel
2000-06-15 13:01 C Compiler Vince Heflin
2000-06-15 13:19 ` Philipp Thomas
2000-04-26 10:30 Ralph Wang
2000-04-26 11:39 ` Martin v. Loewis
1999-09-12 18:30 c++ compiler BPalencia
1999-09-13  0:10 ` Gerald Pfeifer
1999-09-30 18:02   ` Gerald Pfeifer
1999-09-30 18:02 ` BPalencia
1998-09-29 21:55 C compiler Johnny T

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=C38EC5EA58E6D111AA690001FA7EEEC9112617@s02mks6.ham.airbus.dasa.de \
    --to=christine.grafe@airbus.dasa.de \
    --cc=gcc@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).