Why Do C/C \'s cos() and sin() Functions Produce Unexpected Results for Common Angles Like 180 Degrees?

Unexpected Results from C/C 's cos() and sin() for Familiar Angles

When applying an angle of 180 degrees to C/C 's cos() and sin() functions, an incorrect outcome may arise. This could be surprising since we anticipate the results to be:

• sin of 0.0547
• cos of 0.99

However, the actual results often differ:

• sin of 3.5897934739308216e-009
• cos of -1.00000

This discrepancy stems from the fact that cos(a), sin(a), and tan(a) functions in C/C expect radians as an argument, not degrees. The conversion from 180 degrees to radians can sometimes introduce an approximation.

Even with the correct radian calculation, the results may still deviate due to the finite precision of double and a potential misrepresentation of PI.

To address this, it's best to reduce the argument in degrees before invoking the trig function. By limiting the angle to between -45° and 45°, we ensure the accuracy of the outcome.

For instance, consider the following code, which calculates sin() in degrees using argument reduction:

#include <math.h>
#include <stdio.h>

static double d2r(double d) {
  return (d / 180.0) * ((double) M_PI);
}

double sind(double x) {
  if (!isfinite(x)) {
    return sin(x);
  }
  if (x <p>This code generates a more accurate result than the original approach, especially for values at multiple angles, because it performs argument reduction before calling the trig function.</p></stdio.h></math.h>

The above is the detailed content of Why Do C/C \'s cos() and sin() Functions Produce Unexpected Results for Common Angles Like 180 Degrees?. For more information, please follow other related articles on the PHP Chinese website!