those damn warnings!!!

( I'm using Visual Studio 2003 .NET )
In all of my programs i get thousand's of this warnings ( in my Task List )

: warning C4244: 'argument' : conversion from 'double' to 'int', possible loss of data

and they ........ me off!
How can i get rid of them???
For example i got an int a, a have to assign a new value for example 8/7.
I let it go like this, my a = 1, but i get a warning. Is there a possible way to fix this???

And is it Ok to leave a program with so many warnings?
If it's ok just tell me the way to turn their display off.

those warnings appear for good reason -- the way to get rid of them is to correct your code. Many (most) warnings that appear in YOUR code are really errors and should be treated as such.

you can also use #pragma to turn off specific warnings. Put this before any includes except stdafx.h

Code:

---

#pragma warning(disable: 4244)

---

So tell me how can i fix the above example.
Is there alternative???

you could cast to the right type like

Code:

---

double a = 7.0;
int b = 2;
int res = (int)(a/b);

---

or better

Code:

---

int res = static_cast<int>(a/b);

---

If you really want to convert a double to an int.
Kurt

Allright thats cool. But writing all those (int) is really boring...
But can this little warning do anything serius.
Anyway the type is converted automaticly.
And i do Fix every warning that isn't conversion related!

Quote:

---

For example i got an int a, a have to assign a new value for example 8/7.
I let it go like this, my a = 1, but i get a warning. Is there a possible way to fix this???

---

Yeah, when you're going to chop off the decimal part of the number, which is what happens when you assign a fraction to an int variable, tell the compiler and everyone that reads your code that you really intended for that to happen:

Code:

---

int a = static_cast<int>(8/7);

---

> How can i get rid of them???
Well if you have so many, then it seems to me you just threw the code together without any regard as to whether you chose the correct types for things. Carefully chosen types will tell you a lot more when you start to do dumb things like add apples to oranges, which would otherwise go un-noticed until much later.

Or you were using a less fussy compiler and now you're only just discovering the results of your sloppy coding practices.

It's one of the hazards of learning the compiler as opposed to learning the language. Change your compiler and you have to start all over again. Sooner or later, most people realise this approach sucks and they try and learn the language first.

> and they ........ me off!
And we have a phrase "a poor workman blames his tools".

Quote:

---

Originally Posted by Ancient Dragon

Code:

---

#pragma warning(disable: 4244)

---

---

That helped, Thanks!

Quote:

---

Originally Posted by ElastoManiac

And i do Fix every warning that isn't conversion related!

---

yes, you should make every effort to correct the problem(s). If you don't most of them will probably cause serious runtime errors.

Quote:

---

Originally Posted by Ancient Dragon

you can also use #pragma to turn off specific warnings. Put this before any includes except stdafx.h

Code:

---

#pragma warning(disable: 4244)

---

---

That's probably only for MSVC, although I don't know for sure.

Quote:

---

Originally Posted by dwks

That's probably only for MSVC, although I don't know for sure.

---

Probably -- but that is the compiler he is using.

Yes, I know, but [s]he's not the only one reading this thread. :)

hehehe
http://img322.imageshack.us/img322/4170/ss2ae.jpg