There are some advantages also for taking Pi/2 as the circle constant.
The choice between 2xPi and Pi/2 is equivalent with the choice between the cycle and the right angle as the unit of plane angle (the right angle corresponds with the "imaginary" unit, i.e. any point on the unit circle corresponds to i^x, with x in right angles). When extended to 3 dimensions, the corresponding constants for the solid angle become 4xPi and Pi/2, so Pi/2 is more consistent (it corresponds to taking the orthogonal trihedron as the unit of solid angle). The consistency of Pi/2 remains true for higher-dimensional spaces, but that has little practical importance.
"Pi" is by far the worst choice, in all computational applications either 2xPi or Pi/2 are needed, not Pi.
The only case where Pi appears naturally is in measurements, because both the circumference and the diameter are much easier to measure than the radius, and Pi is the relationship between these 2 practical measurements, allowing the conversion of one to the other.
Nowadays, the computational uses of Pi are many orders of magnitude more frequent than the conversions between the practical measurements of diameter and circumference, so the use of Pi is undesirable inside computer programs or in symbolic processing of mathematical formulae.
In general, it is much better to implement trigonometric functions where the argument is either x*Pi/2 or x*2*Pi, instead of traditional trigonometric functions, because the argument reductions are fast and exact. Sadly, the floating-point arithmetic standard defines useless functions of Pi*x, like sinPi, cosPi etc., instead of using any of the 2 better choices.
The only possible advantage of traditional trigonometric functions is at integration or differentiation, where they could save a multiplication, but in almost all applications of this kind the argument of the function is not x, but an expression with at least one multiplication, and the additional multiplication with a constant caused by using x*Pi/2 or x*2*Pi can frequently be done at compile time, or at run time, but only once, not at every computation.
The choice between 2xPi and Pi/2 is equivalent with the choice between the cycle and the right angle as the unit of plane angle (the right angle corresponds with the "imaginary" unit, i.e. any point on the unit circle corresponds to i^x, with x in right angles). When extended to 3 dimensions, the corresponding constants for the solid angle become 4xPi and Pi/2, so Pi/2 is more consistent (it corresponds to taking the orthogonal trihedron as the unit of solid angle). The consistency of Pi/2 remains true for higher-dimensional spaces, but that has little practical importance.
"Pi" is by far the worst choice, in all computational applications either 2xPi or Pi/2 are needed, not Pi.
The only case where Pi appears naturally is in measurements, because both the circumference and the diameter are much easier to measure than the radius, and Pi is the relationship between these 2 practical measurements, allowing the conversion of one to the other.
Nowadays, the computational uses of Pi are many orders of magnitude more frequent than the conversions between the practical measurements of diameter and circumference, so the use of Pi is undesirable inside computer programs or in symbolic processing of mathematical formulae.
In general, it is much better to implement trigonometric functions where the argument is either x*Pi/2 or x*2*Pi, instead of traditional trigonometric functions, because the argument reductions are fast and exact. Sadly, the floating-point arithmetic standard defines useless functions of Pi*x, like sinPi, cosPi etc., instead of using any of the 2 better choices.
The only possible advantage of traditional trigonometric functions is at integration or differentiation, where they could save a multiplication, but in almost all applications of this kind the argument of the function is not x, but an expression with at least one multiplication, and the additional multiplication with a constant caused by using x*Pi/2 or x*2*Pi can frequently be done at compile time, or at run time, but only once, not at every computation.