Mailinglist Archive: opensuse (3103 mails)

< Previous Next >
Re: [SLE] gcc and ostream problem.
  • From: Andre Truter <andre.truter@xxxxxxxxxxxxx>
  • Date: Mon, 10 Feb 2003 17:05:06 +0200
  • Message-id: <20030210170506.4de5d2b0.andre.truter@xxxxxxxxxxxxx>
On Mon, 10 Feb 2003 09:48:30 -0500
Jerry Feldman <gaf@xxxxxxxxxxx> wrote:

> Time to fall on your sword :-)
> g++ 3.0 now supports the ANSI standard. One of the things you will need
> to do is to add "using" statements, such as "using namespace std".
>

Aaarrgg!!
I was afraid that the code was way too outdated after I saw the compiler's initial warnings about backward compatibility.

> I ran into this same problem last year with a customer (commercial Unix)
> who has millions of lines of code. The solution was to backport gcc
> 2.9.5 to the system. However, one problem with backporting an older
> compiler is that you become out of sync with the linker and other parts
> of the compilation system.
>

I suppose I will have to start getting the code up to standards. :-/

Thanks.

/* Goes off in search of my sword.. */

--
Andre Truter
Software Engineer
Registered Linux user #185282
ICQ #40935899 AIM: trusoftzaf
http://www.trusoft.za.net

<------------------------------------------------->
< The box said: Requires Windows 95 or better... >
< So I installed Linux >
<------------------------------------------------->

Disclaimer and Confidentiality Warning

This message is intended for the addressee only. If you are not the intended recipient of this message, you are notified that any distribution, use of or copying of this communication is strictly prohibited. If you have received the communication in error, please notify the sender immediately. The views and opinions expressed in this message are those of the individual sender of this message and do not necessarily represent the views and opinions of ATIO. Consequently, ATIO does not accept responsibility for such views and opinions and this message should not be read as representing the views and opinions of ATIO without subsequent written confirmation. Each page attached hereto must also be read in conjunction with this disclaimer.


< Previous Next >