From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27447 invoked by alias); 26 Oct 2007 14:08:27 -0000 Received: (qmail 27434 invoked by uid 22791); 26 Oct 2007 14:08:25 -0000 X-Spam-Check-By: sourceware.org Received: from chip2og50.obsmtp.com (HELO chip2og50.obsmtp.com) (64.18.13.37) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 26 Oct 2007 14:08:18 +0000 Received: from source ([192.150.11.134]) by chip2ob50.postini.com ([64.18.5.12]) with SMTP; Fri, 26 Oct 2007 07:08:08 PDT Received: from inner-relay-3.eur.adobe.com (inner-relay-3.adobe.com [192.150.20.198] (may be forged)) by outbound-smtp-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id l9QE64IQ016875; Fri, 26 Oct 2007 07:06:05 -0700 (PDT) Received: from apacmail.pac.adobe.com (apacmail.pac.adobe.com [130.248.36.99]) by inner-relay-3.eur.adobe.com (8.12.10/8.12.9) with ESMTP id l9QE7uFZ025772; Fri, 26 Oct 2007 07:08:01 -0700 (PDT) Received: from namailgen.corp.adobe.com ([10.8.192.91]) by apacmail.pac.adobe.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 26 Oct 2007 23:07:58 +0900 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: egcs help Date: Fri, 26 Oct 2007 14:31:00 -0000 Message-ID: References: From: "John (Eljay) Love-Jensen" To: "Steve Stevenson" , X-IsSubscribed: yes Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org X-SW-Source: 2007-10/txt/msg00344.txt.bz2 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? Most likely, the code needs to be ported from "EGCS's proto-C++" to complia= nt C++ (ISO 14882). > I understand the EGCS was merged back into the g++ fold... Correct. > ... but g++ as currently developed doesn't like the code. GCC's C++ has become more-and-more compliant to the ISO 14882 standard over= the versions & years. 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 proce= ss. There was substantial churn during the C++ standardization process, su= ch 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 establ= ished core C++-isms which have made it into the standard, or the lunatic fr= inge of proto-C++-isms which did not make it into the standard. HTH, --Eljay