Re^2: Perl oddities by merlyn (Sage) on Mar 01, 2005 at 18:05 UTC 
sin, cos, and atan2 are "primitive" functions. From those, all other forward and reverse functions can be trivially derived.
The overhead of calling a subroutine is tiny compared to the overhead of computing the sin or cos, I would imagine.
 [reply] 

sin, cos, and atan2 are "primitive" functions.
Well, once you have a routine for sin, then cos is the same thing, but pi/2 sooner. And I'm fairly sure that's the way it's implemented in the libraries.
Using atan2 to do an inverse sin or cos is a bit of a walk in the park, but essentially I guess you have to find the 'Y' value once you have the 'X', then submit both to atan2, and that will give you the angle you're looking for.
That's a nice brain exercise right after lunch.
Alex / talexb / Toronto
"Groklaw is the opensource mentality applied to legal research" ~ Linus Torvalds
 [reply] [d/l] [select] 

I suspect on most CPUs, it just uses the sin and cos opcodes of the native CPU. Implementing sin in terms of cos (or viceversa) is just asking for problems, like the wellknown results being a little off, since pi/2 cannot be exactly represented as a float (or as anything else in finite RAM).
 [reply] 

I know. But you can do away with either sin or cos as well  they are the same primitive, just shifted a quarter of a phase. That of course doesn't mean tan couldn't be present. After all, Perl gives us
push, pop, shift and unshift, when they can all be trivially implemented using splice. Perl is a rich language, and any minimal approach is, to quote brian, what I consider exceptions to normal Perl thinking. Normal Perl thinking is "programmer convenience". A minimalistic approach isn't programmer convenience.
 [reply] 

Howdy!
My sense is that push/pop/shift/unshift are much more frequently
used than the trig functions. On that basis, it makes Huffman sense
to provide the convenience of the push, etc. functions while declining
to provide a fuller set of trig functions.
 [reply] 



Re^2: Perl oddities by fizbin (Chaplain) on Mar 03, 2005 at 23:38 UTC 
Note that I've seen the pattern of providing sin, cos and atan (but not other trig functions) in other libraries and programming languages. And the reason for this (that so far as I can tell no one has yet said) is simple: those functions are defined for all values of their argument. tan isn't. arcsin and arccos aren't.
Not that it's necessarily a very good reason, mind you.

@/=map{[/./g]}qw/.h_nJ Xapou cets krht ele_ r_ra/;
map{y/X_/\n /;print}map{pop@$_}@/for@/
 [reply] [d/l] [select] 

And the reason for this (that so far as I can tell no one has yet said) is simple: those functions are defined for all values of their argument. tan isn't. arcsin and arccos aren't.
Well, division isn't defined for all values of its arguments either, and neither are log and sqrt. So, I agree it's not much of a reason at all.
 [reply] 