Bug: solve(), nsolve() and fsolve() depend on angle mode?

[CR Haeger]

(02-15-2014 12:41 PM)Tugdual Wrote:  Two comments:
- variable definitions are x in CAS and X in Home (even if you tell on which variable you solve, I know this is weird)
- most of the solve functions require an expression with '=' sign. In the best case you'll get a warning telling you that it assumes "=0" otherwise you just don't know what happens

Now, I played with your example and didn't find a connection with use of degrees/radians but the solve functions are extremely chaotic for sure and the help quite inexistant.

Thanks for your comments and looking at this. Yep, I know about x vs X as CAS vs Home variables. It also seems that you don't always need the "=" sign in the expression. As others have posted - I wish there were a "help popup or tool-tip" that was available when selecting these functions...

I'm still seeing these errors in HOME depending on degree/radians settings. I hope this gets looked at as it can be convenient to run these solve functions from HOME - but less so if I have to check to be in radians mode.