TURN BACK.
Visual C++ 6.0 doesnt compile all C++ code.
Its old...and it will INTERNAL COMPILER ERROR, and give you warnings where you shouldnt get them, and not give you warnings where you should get them.
I used it for over a year trust me!
Because Microsoft make devlopers pay fore new releases rather than upgrade, this sad piece of non-standard not-C++ anymore crap is still floating around, and in widespread use.
sad.
Very sad.
Just imagine you wrote a big library, and wanted to share it with everyone, only the only person who could compile it was you.
Or say you wanted to write some awsome metaprogrammed libraries, but they didnt work because partial specification and covariant return types hadnt been invented when 6.0 was made.
Intellisense and browse-details is all you've got to look forward to, and although when i quit i missed it like a drug, i soon got over it and feel im actually better withought such things.
I organise my code more properly, simplify it, and can find things just as quick (and not get pissed off when it does work, eg: after an '>' operator, intellisense doesnt work unless the a>b is wrapped in brackets like so (a)<(b) ... And many more quirks which infected and damaged my programming habits: Most noticably having massive stretches of code in one big file, because i had browse info to take me to functions).
Its much better to be able to use your code just as fast based on its intelligent naming choices, and well arranged files and chunking.
That way, using the code will be easier for you, and others.
..Just disable DevC++'s fat-shady member-window, or get Code::Blocks and do so with its.
...Or buy VC++7.0 if yourdesire to become lazy, and have less need to write competent and -abstract memorable names (going against all that c++ programming stands for) is making you sweat with anguish, fear and excrutiating pain.
>.<.
( Its all real harsh, but its all really real. )
