G++ problems

[Karlos]

I think for the majority of beginners, "using namespace std;" is the least hassle. There really isnt much n the standard C library or the C++ STL where you'd ever get indentifier overlaps requiring the selection of a particular member of a given namespace...

That only really tnds to happen in large projects involving many people who always end up inventing the same names for stuff, or in various 3rd party libraries which offer replacement functionality for elements of the standard libraries.

[Karlos]

@alx

#include is definately erronious :-)

C++ formatted IO streams are cack for console output anyway. Coming from me, Mr. "C++ owns all progrmming languages", thats quite a statement!

I mean theyr'e great for quick and dirty use, but in all honesty, I find the old C printf() a lot more useful, but as with all things C, you have no protection from misusing it...

[Karlos]

I just downloaded that big fat 85Mb GoldEd trial. It comes with gcc 2.95.3 and 3.3 (plus vbcc and other goodies).

I haven't installed it yet, but I hear it does most of the set up for you (the main reason I downloaded the bugger - 85Mb over 56k....)

I always find manual installation of gcc a total nightmare. Guess I am simply not a l33t haXX0r.

Still, on the bright side, I am not a l33t haXX0r, thus implying I have real friends, good lady and a life away from my unix box :lol:

[Karlos]

@alx

Yeah, Kronos is right - it has a restriction on the source file length, but the compilers are complete.

Personally I don't mind StormEd for source editing - I got pretty used to it so any restriction in GoldEd's editor doesnt really matter to me.