Strange numbers like 3.1415f ...

nitroman · Post by **nitroman** » Sat Jul 31, 2004 7:30 pm

In the examples, there is a lot of numbers that are used and I don't know what they mean...

for example:

smgr->addCameraSceneNodeFPS(0,100.0f,300.0f);
camera->setFOV(3.1415f)
//etc, etc, etc...

why there is a "f" after 3.1415???

I use those numbers without knowing their meanings so I can't adjust them...

Can you give me explanations, I'm confused...

Fussel · Post by **Fussel** » Sat Jul 31, 2004 7:35 pm

its a float value..
depending on what you need you can take different types of numbers..for example int (1,2,3...) float, etc..dont know a good tutorial on this, but try a search with google

hearsedriver · Post by **hearsedriver** » Sat Jul 31, 2004 7:39 pm

This magic number is the constant PI, which is 180 degrees in radians. The f behind the number helps the compiler to distinguish 32-bit floats and 64-bit doubles. Because setFOV expects floats, and the compiler assumes 64-bit double for floating point constants without the "f", using the constant without the "f" would result in a compiler-warning that the precision will be lost when passing it to a function that uses floats.

HTH
Matt

nitroman · Post by **nitroman** » Sat Jul 31, 2004 8:09 pm

Ok I understand. It wasn't so complicated.

so

camera->setFOV(3.1415f)

is the same thing as:

float myfloat= 3.1415
camera->setFOV(myfloat)

?

warui · Post by **warui** » Sat Jul 31, 2004 10:18 pm

Yes. 'f' after the number forces compiler to treat it as a float value.

nitroman · Post by **nitroman** » Sun Aug 01, 2004 1:48 am

thanks