public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ingo Krabbe <ingo.krabbe@eoa.de>
To: gcc-help@gcc.gnu.org
Cc: "Steve Stevenson" <fatmarauder@mac.com>
Subject: Re: egcs help
Date: Tue, 30 Oct 2007 04:34:00 -0000	[thread overview]
Message-ID: <200710300411.12175.ingo.krabbe@eoa.de> (raw)
In-Reply-To: <EDC8DDD212FEB34C884CBB0EE8EC2D9103B25DAA@namailgen.corp.adobe.com>

Am Freitag, 26. Oktober 2007 16:07:53 schrieb John (Eljay) Love-Jensen:
> Hi Steve,
>
> > A colleague wants to use a piece of software developed in the 1990s, but
> > written EGCS.  Is there help in getting this going?
>
[...]

> As I recall, EGCS was a splinter effort due to frustration that GCC wasn't
> keeping up with the rapid evolution of C++ during the standardization
> process.  There was substantial churn during the C++ standardization
> process, such that it was a very difficult moving target to pin down.
>
> Since C++ was standardized, GCC has become much, much more compliant with
> C++.
>
> Old EGCS is not very C++ compliant.  And code based upon it may also be not
> very C++ compliant, depending if that code used (at that time) well
> established core C++-isms which have made it into the standard, or the
> lunatic fringe of proto-C++-isms which did not make it into the standard.

The best way to use such old code (if I were you, the only way) is to detect 
the problems that rise from breaking the standard and redevelop this old 
Software package.

This might be quite few work, depending on how much models need to be touched.

bye

ingo

>
> HTH,
> --Eljay



-- 

Mit freundlichen Grüßen / kind regards

I n g o   K r a b b e
System Administrator / system administrator
_________________________________________________________________________
Elements of Art GmbH         http://www.eoa.de
An der Eickesmuehle 22       41238 D-Moenchengladbach / Germany
fon: +49 (2166) 91567-3418   Registergericht: Moenchengladbach HRB 5855
fax: +49 (2166) 91567-99     Geschaeftsfuehrer: Erik Winterberg,
                                                Sebastian Leppert

      reply	other threads:[~2007-10-30  3:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-26 14:08 Steve Stevenson
2007-10-26 14:31 ` John (Eljay) Love-Jensen
2007-10-30  4:34   ` Ingo Krabbe [this message]

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=200710300411.12175.ingo.krabbe@eoa.de \
    --to=ingo.krabbe@eoa.de \
    --cc=fatmarauder@mac.com \
    --cc=gcc-help@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).