Trigonometry in Feature Requests
proc/tan(x) return sin(x)/cos(x)
If they were listed in the reference pages, you wouldn't need to include, or point somebody to an arbitrary library. You would simply need to copy and paste a single line of officially provided code into your source from the related help page.
They could be included for completeness, but I see no reason for this to be a priority, or a necessary addition.
Which begs the question: why include the code of functions in the reference and not implement them? This is confusing and silly.
Because its much more complicated for them to implement it into the compiler than it is to write a plain text line in a help file
Even so, it really isn't hard to get most of the trigonometric functions, and I'm sure someone has a library with them, somewhere.
proc/tan(theta) return sin(theta) / cos(theta)proc/cot(theta) return cos(theta) / sin(theta)proc/sec(theta) return 1 / cos(theta)proc/csc(theta) return 1 / sin(theta)proc/atan(x) return arccos(1 / sqrt(1+x*x))proc/acot(x) return arcsin(1 / sqrt(1+x*x))proc/asec(x) return arccos(1 / x)proc/acsc(x) return arcsin(1 / x)
If you're after this for completeness's sake, why are you stopping at trig functions?
Also, there aren't a whole lot of three- or four-letter proc names, so there's a decent chance that someone would have a function in their game that they'd like to abbreviate as "sec" or "csc".
It's best to have these be in a library, so people can include them as needed.
Then they should get some proper naming standards.
It is not best to have something in a random library, especially not something this simple that should have been built in from the start.
These are typical names for math functions, so it'd be detrimental to use any other names.
but the other ones aren't needed and are better put in a library.