From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12622 invoked by alias); 12 Mar 2010 17:38:00 -0000 Received: (qmail 12608 invoked by uid 22791); 12 Mar 2010 17:38:00 -0000 X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from exprod6og109.obsmtp.com (HELO exprod6og109.obsmtp.com) (64.18.1.23) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 12 Mar 2010 17:37:55 +0000 Received: from source ([192.150.11.134]) by exprod6ob109.postini.com ([64.18.5.12]) with SMTP ID DSNKS5p78OpP4LsXpz8vzNYxgXNAAeO2RnB4@postini.com; Fri, 12 Mar 2010 09:37:55 PST Received: from inner-relay-2.corp.adobe.com ([153.32.1.52]) by outbound-smtp-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id o2CHTj18019080; Fri, 12 Mar 2010 09:29:46 -0800 (PST) Received: from nacas02.corp.adobe.com (nacas02.corp.adobe.com [10.8.189.100]) by inner-relay-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id o2CHbp06016030; Fri, 12 Mar 2010 09:37:51 -0800 (PST) Received: from nambxv01a.corp.adobe.com ([10.8.189.95]) by nacas02.corp.adobe.com ([10.8.189.100]) with mapi; Fri, 12 Mar 2010 09:37:51 -0800 From: "John (Eljay) Love-Jensen" To: Jangid , "gcc-help@gcc.gnu.org" Date: Fri, 12 Mar 2010 19:12:00 -0000 Subject: RE: Error after installing new version of gcc Message-ID: <4B7A6CC9992C4E4FB188D02872C90A6B134F44@nambxv01a.corp.adobe.com> References: <27879757.post@talk.nabble.com> <4B7A6CC9992C4E4FB188D02872C90A6B134F42@nambxv01a.corp.adobe.com>,<27880345.post@talk.nabble.com> In-Reply-To: <27880345.post@talk.nabble.com> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 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: 2010-03/txt/msg00178.txt.bz2 Hi Manoj, If your non-compliant C++ code worked on a C++ compiler that happened to be= lax (i.e., allowed non-compliance), as I see it your two choices are: + continue to use the lax C++ compiler + make your non-compliant C++ code C++ compliant My expectation is that the non-compliant C++ code which is brought into com= pliance should still work on the older compiler without issue. Sincerely, --Eljay