STL with gcc3

STL with gcc3

[Ji Li]

Hello,

	I am experiencing some problem with STL when compile with gcc3. I
have a little piece of c++ code like this:

	#include <iostream>
	#include <string>

	int main(){
	string aa = "Hello World !";

	cerr << aa << endl;
	}

	If I compile it with gcc-2.96, there is no problem. However, when
I compile it with gcc-3.0.4, the compiler does not recognize neither
'string' nor 'cerr'. But if I add 'using namespace std;', gcc-3.0.4 works
fine with it.

	I believe there must be a way to make gcc-3.0.4 backward
compatable but just could find it. Would you please point the way for me?
Thanks a lot.

Regards.

Ji Li                              _/_/_/_/_/     _/
Physics Department                        _/     _/ 
Rensselaer Polytechnic Institute         _/     _/ 
Tel:(757)269-5328(JLab Office)      _/_/_/     _/_/_/_/_/

Re: STL with gcc3

[Matt Austern]

On Wednesday, July 17, 2002, at 11:35 AM, Ji Li wrote:

>
> Hello,
>
> 	I am experiencing some problem with STL when compile with gcc3. I
> have a little piece of c++ code like this:
>
> 	#include <iostream>
> 	#include <string>
>
> 	int main(){
> 	string aa = "Hello World !";
>
> 	cerr << aa << endl;
> 	}
>
> 	If I compile it with gcc-2.96, there is no problem. However, when
> I compile it with gcc-3.0.4, the compiler does not recognize neither
> 'string' nor 'cerr'. But if I add 'using namespace std;', gcc-3.0.4 
> works
> fine with it.
>
> 	I believe there must be a way to make gcc-3.0.4 backward
> compatable but just could find it. Would you please point the way for 
> me?

You really don't want to do that.  The standard says that everything
in the Standard Library is supposed to be in namespace std.  Other
compilers have conformed to the standard for years.  You should
change your code, for portability if for no other reason.

			--Matt

Re: STL with gcc3

[Phil Edwards]

On Wed, Jul 17, 2002 at 11:39:53AM -0700, Matt Austern wrote:
> On Wednesday, July 17, 2002, at 11:35 AM, Ji Li wrote:
> >
> > 	I believe there must be a way to make gcc-3.0.4 backward
> > compatable but just could find it. Would you please point the way for 
> > me?
> 
> You really don't want to do that.  The standard says that everything
> in the Standard Library is supposed to be in namespace std.  Other
> compilers have conformed to the standard for years.  You should
> change your code, for portability if for no other reason.

Matt is correct; your code is not C++.  To aid in making the transition, gcc
3.x lets you include <backward/iostream.h>.  But there is no comparable header
for <string>, since there was never really a pre-standard string class.  So
you'll have to edit your code anyway; may as well fix the I/O names as well.


Phil

-- 
If ye love wealth greater than liberty, the tranquility of servitude greater
than the animating contest for freedom, go home and leave us in peace.  We seek
not your counsel, nor your arms.  Crouch down and lick the hand that feeds you;
and may posterity forget that ye were our countrymen.            - Samuel Adams

Re: STL with gcc3

[Ji Li]

Hi,

	Yes I get the idea. The question is the real code that I am
dealing with is far more comlex than the example I gave here. Ok, I will
try to change the code. Thanks to you all for your help.

Ji Li                              _/_/_/_/_/     _/
Physics Department                        _/     _/ 
Rensselaer Polytechnic Institute         _/     _/ 
Tel:(757)269-5328(JLab Office)      _/_/_/     _/_/_/_/_/

On Wed, 17 Jul 2002, Phil Edwards wrote:

> On Wed, Jul 17, 2002 at 11:39:53AM -0700, Matt Austern wrote:
> > On Wednesday, July 17, 2002, at 11:35 AM, Ji Li wrote:
> > >
> > > 	I believe there must be a way to make gcc-3.0.4 backward
> > > compatable but just could find it. Would you please point the way for 
> > > me?
> > 
> > You really don't want to do that.  The standard says that everything
> > in the Standard Library is supposed to be in namespace std.  Other
> > compilers have conformed to the standard for years.  You should
> > change your code, for portability if for no other reason.
> 
> Matt is correct; your code is not C++.  To aid in making the transition, gcc
> 3.x lets you include <backward/iostream.h>.  But there is no comparable header
> for <string>, since there was never really a pre-standard string class.  So
> you'll have to edit your code anyway; may as well fix the I/O names as well.
> 
> 
> Phil
> 
> -- 
> If ye love wealth greater than liberty, the tranquility of servitude greater
> than the animating contest for freedom, go home and leave us in peace.  We seek
> not your counsel, nor your arms.  Crouch down and lick the hand that feeds you;
> and may posterity forget that ye were our countrymen.            - Samuel Adams
> 

Re: STL with gcc3

[Gabriel Dos Reis]

Ji Li <liji@jlab.org> writes:

| Hi,
| 
| 	Yes I get the idea. The question is the real code that I am
| dealing with is far more comlex than the example I gave here. Ok, I will
| try to change the code. Thanks to you all for your help.

As a transition, you might want to start with a "using namespace std;" right
after the includes.

-- Gaby

Re: STL with gcc3

[Joe Buck]

Ji Li writes:
> 	I am experiencing some problem with STL when compile with gcc3. I
> have a little piece of c++ code like this:
> 
> 	#include <iostream>
> 	#include <string>
> 
> 	int main(){
> 	string aa = "Hello World !";
> 
> 	cerr << aa << endl;
> 	}

As has been pointed out, this won't compile with almost any current
C++ compiler from any vendor.

> 	If I compile it with gcc-2.96, there is no problem. However, when
> I compile it with gcc-3.0.4, the compiler does not recognize neither
> 'string' nor 'cerr'. But if I add 'using namespace std;', gcc-3.0.4 works
> fine with it.

And so will gcc-2.95.x and Red Hat's gcc-2.96.  As a transition aid, those
compilers had a flag called honor_std which is false by default.  When
honor_std is false, specifying std::cout will look for cout instead, and
using directives that bring part or all of the std namespace into the
global namespace are ignored.

The intent was to get programmers started in writing their C++ code the
right way.  Unfortunately, there are too many Unix/Linux/BSD hackers who
never used a C++ compiler other than GNU and kept blithely kept coding the
old way.

> 	I believe there must be a way to make gcc-3.0.4 backward
> compatable but just could find it. Would you please point the way for me?

Make your code backward compatible instead.  If you need for your code to
build with older GNU compilers as well as current compilers (from GNU
and/or others), put in the line "using namespace std;" or say std::string,
std::cerr and std::endl.  The resulting code will work with both old and
new compilers.

The std namespace has been standard for four years now and in the draft
standard for a few years before that.  Sorry, time's up.  Time to write
real C++ code.