07-26-2018, 07:01 PM

rectangular_coordinates(-(sqrt(2)),(π/4)) ==> [-1,-1]

polar_coordinates(-1,-1) ==> [sqrt(2),(3/4)*π]

polar_coordinates([-1,-1]) ==> [sqrt(2),(-3/4)*π]

polar_coordinates() expects a point, and returns a vector.

rectangular_coordinates() expects a vector and returns a vector.

This is confusing for infrequent users of these commands. The polar_coordinates() command can lead to an incorrect result, if a vector is supplied as the argument, such as might be the case if the result of rectangular_coordinates() was being re-used there.

NOTE: I was using the emulator, and I have been noticing some odd behaviors (including the above). After performing a reset, I am now getting the same result from polar_coordinates() whether or not a point or vector is used. I apologize for this diversion!

-Dale-

polar_coordinates(-1,-1) ==> [sqrt(2),(3/4)*π]

polar_coordinates([-1,-1]) ==> [sqrt(2),(-3/4)*π]

polar_coordinates() expects a point, and returns a vector.

rectangular_coordinates() expects a vector and returns a vector.

This is confusing for infrequent users of these commands. The polar_coordinates() command can lead to an incorrect result, if a vector is supplied as the argument, such as might be the case if the result of rectangular_coordinates() was being re-used there.

NOTE: I was using the emulator, and I have been noticing some odd behaviors (including the above). After performing a reset, I am now getting the same result from polar_coordinates() whether or not a point or vector is used. I apologize for this diversion!

-Dale-