Thread: Borland bug

Hey try this:

Code:

#include <iostream.h>
#include <math.h>

int main(void)
{
  cout << cos(90);
  return 0;
}

The answer I get is -0.448074, instead of 0. This seems to be consistent throughout all Borland compilers, even with their latest release. It's seriously ruining my matrix calculations. Any thoughts?

I'm just guessing, but it looks like the cos() uses radians. Try

Code:

#include <iostream.h>
#include <math.h>
#define PI 3.141592654

int main(void)
{
  cout << cos(PI/2);
  return 0;
}

>The answer I get is -0.448074.
And this is unexpected, how?

>but it looks like the cos() uses radians
Yes, it does. This is well documented too.

also, try something like this:

Code:

float cosdeg(float deg)
{
    return cos(deg * (PI/180));
}

Try using that function with degrees (like 90 in your example). I'm surprised if borland's math.h doesn't have trig functions that use degrees.

Originally posted by Prelude
>>but it looks like the cos() uses radians
Yes, it does. This is well documented too.

Sorry Prelude, haven't used them so wouldn't know. Was just guessing.

Checked my Borland compiler. It doesn't say anything about cos() using deg or rad parameters, so I assumed it's deg. However, the acos() function returns a radian, so now I'm kinda confused. I'll try your cosdeg() idea neandrake.

Great, tell me how it goes

> And that means some of my programs I submitted in class 2 years ago were incorrect
Should you be worried if your tutors failed to spot them?
How wrong could a program be before they notice I wonder...