omg.. compiler hates me

Code:

/* Quest Open RPG
 * Ryan Oldenburg
 * Completion: 15%
 * Version 1.0
 */

#include <windows.h>
#include <iostream>
#include <string>
#include "class.h"

using namespace std;
using std::string;

//Constructor
player::player(int healthv, 
               int weaponv, 
               int shieldv, 
               int arrowsv, 
               int magicv, 
               int bombsv, 
               int goldv, 
               int bowv) : health(healthv), 
                           weapon(weaponv), 
                           shield(shieldv), 
                           arrows(arrowsv), 
                           magic(magicv), 
                           bombs(bombsv), 
                           gold(goldv), 
                           bow(bowv)
{

}

//Acual Program
int main()
{
//Location Variables
int x;
int y;

//Introduction
string title = "Quest Open RPG";

for(int a = 0; title[a] != '\0'; a++)
{
     cout << title[a];
     Sleep(50);
}

return 0;
}

nothing wrong with that right? look at the errors i get:

Linker Error unidentified refrence to 'cout'
Linker Error unidentified refrence to 'ostream:perator<<(char)'
Linker Error unidentified refrence to 'endl(ostream&)'
Linker Error unidentified refrence to 'cerr'
Linker Error unidentified refrence to 'ostream:perator<<(char const *);
Linker Error unidentified refrence to '__out_of_range(char const *)'
Linker Error unidentified refrence to '__length_error(char const *)'

Build Error Project.exe Error 1

but i dont get any when i remove windows.h from the include and remove Sleep(50); ..... what the hell is goin on?! thanx

Two things:
1. Do you really need windows.h and sleep(50) in your program? If not, you could just remove them and compile peacefully.
2. What compiler are you using?

Could be a namespace issue.

Code:

using namespace std;
using std::string;

dev c++, im using Sleep(50) to make it a typing effect, if you have any other ideas, ill use it instead

I used to use Dev-C++, but then it refused to compile anything with #include <iostream.h>, so I moved onto Borland's free compiler. You have to compile from the command line, but it isn't as bad as it sounds. The hardest part is getting it set up, as Borland's documentation is not that clear.


EDIT:Fixed glaring typoes.

hehe, what a pitiful compiler if it cant use the most basic of includes......

This compiles and runs on mingw. Can you write out
not just the warnings but the command line arguments
used to invoke the compiler and linker?

Code:

/* Quest Open RPG
 * Ryan Oldenburg
 * Completion: 15%
 * Version 1.0
 */

#include <windows.h>
#include <iostream>
#include <string>
using namespace std;
using std::string;

class player {
    int health;
    int weapon;
    int shield;
    int arrows;
    int magic;
    int bombs;
    int gold;
    int bow;
public:
    player(int healthv, 
	   int weaponv, 
	   int shieldv, 
	   int arrowsv, 
	   int magicv, 
	   int bombsv, 
	   int goldv, 
	   int bowv);
};

//Constructor
player::player(int healthv, 
               int weaponv, 
               int shieldv, 
               int arrowsv, 
               int magicv, 
               int bombsv, 
               int goldv, 
               int bowv) : health(healthv), 
                           weapon(weaponv), 
                           shield(shieldv), 
                           arrows(arrowsv), 
                           magic(magicv), 
                           bombs(bombsv), 
                           gold(goldv), 
                           bow(bowv)
{

}

int main()
{
    int x;
    int y;

    string title = "Quest Open RPG";

    for(int a = 0; title[a] != '\0'; a++)
    {
	cout << title[a];
	Sleep(50);
    }

    return 0;
}

Originally posted by PHP
hehe, what a pitiful compiler if it cant use the most basic of includes......

no, the moron just set it up wrong

Originally posted by Yawgmoth
I used to use Dev-C++, but then it refused to compile anything with #include <iostream.h>, so I moved onto Borland's free compiler. You have to compile from the command line, but it isn't as bad as it sounds. The hardest part is getting it set up, as Borland's documentation is not that clear.


EDIT:Fixed glaring typoes.

no, the moron just set it up wrong

I agree. You must have set up Dev-C++ wrong if you can't include iostream correctly.

how can i set it up wrong, i just clicked next, next, next and poof done

If you go to the bloodshed forum, you'll see posts about problems with 4.9.7.0. Also, you should've had a choice between teh mingw compiler 2.95 or 3.2. It seems that 3.2 is much more compliant, so you cannot use iostream.h, you have to include <iostream> and then specify either 'using namespace std' or 'using std:cout' (my syntax may be incorrect, but you get the idea0. There have also been problems with the download, I'm not sure exactly what they are, something about files going into an incorrect folder/path. There are posts on how to fix it on the bloodshed forum. I haven't upgraded to 4.9.7, still using 4.9.6.9 which has none of these problems. Once you get all the stuff in the right place it should work quite well. Good luck!

Originally posted by PHP
how can i set it up wrong, i just clicked next, next, next and poof done

I was speaking to Yawgmoth.

Anyways, the original code posted compiles and links correctly with mingw 3.2. Nevermind, just saw Nick's post, same thing I did.

Originally posted by lurker
It seems that 3.2 is much more compliant, so you cannot use iostream.h

i have 3.2 in front of me right here, and it allows <iostream.h> or <iostream>

Sorry for my mistake, I was just going by the posts I've been reading on the bloodshed forum. It seems that if you use
<iostream.h> versus <iostream> that dev-cpp 4.9.7 spits out many, many errors. I am using 4.9.6.9 for now, as it is working without problems for me. Once I have some free time at home to thouroughly understand what I may need to do to get it to work correctly, I'll download 4.9.7. Thanks for the clarification.

Originally posted by Lurker
Sorry for my mistake, I was just going by the posts I've been reading on the bloodshed forum. It seems that if you use
<iostream.h> versus <iostream> that dev-cpp 4.9.7 spits out many, many errors. I am using 4.9.6.9 for now, as it is working without problems for me. Once I have some free time at home to thouroughly understand what I may need to do to get it to work correctly, I'll download 4.9.7. Thanks for the clarification.

a slight word of warning i do not use devc++, just mingw, so if there's any <iostream> vs <iostream.h> problem that is caused by devc++, then i won't know of it