Harlan Grove said:
Seriously, what does everyone think about this?
My immediate impression is that it would cause a tremendous decrease in
the reliability of models. Dates can cause *some* grief, though for most
users it's transparent. But it's also *usually* obvious when a date is
FUBARed - 4 years and a day is an easily recognizable deviation from an
expected value.
With trig functions, however, I suspect that non-engineers/geometers
(and a fair number of engineers as well) would on balance have an
extremely hard time recognizing an incorrect result. How many would
recognize this difference at a glance?
=SIN(40) ===> 0.74511316 (radians mode)
=SIN(40) ===> 0.64278761 (degrees mode)
I agree with the spirit of your suggestion, though. I think I'd rather
see (without any real understanding of the difficulty of implementation)
an optional argument added to trig functions to trigger conversion:
=SIN(90) = SIN(90, 1) ===> 0.893996664
and
=SIN(90, 2) ===> 1.000000000
The downside is that this would break backward compatibility. A more
bloated option would be to add functions (which I've done via add-ins
before):
SIN(90) ===> 0.893996664
SIND(90) ===> 1.000000000