Colin McKay wrote:
> So when there is any chance that ACOS has to work on any number close to 1,
> or -1, a check such as IF VV>1 THEN : VV=1 has to be incorporated on every
> occasion?
>
> Takes some of the slickness off the programming.
Well, working with floating point variables can be ugly. QD
On Tue, May 31, 2016 at 3:16 PM, Norman Dunbar
wrote:
> Hi Colin,
>
> Checking that values are in range in order to call a built in function,
> procedure etc is normal. At least it as been for as long as I've been
> programming - since pre ZX81 days.
>
>
This is definitely a core software enginee
Found it!
SQL> -- Without brackets. Value for A adjusted.
SQL> select power(1.414214,2) - power(4.242641,2) - power(2.828427,2) / (-2 *
4.2426
41 * 2.828427) as answer from dual;
ANSWER
--
-15.68
SQL> -- With brackets. Value for A adjusted.
SQL> select (power(1.414214,2) - p
Hi Colin,
Checking that values are in range in order to call a built in function,
procedure etc is normal. At least it as been for as long as I've been
programming - since pre ZX81 days.
Even now I still check and this includes when writing code to run on my
numerous Oracle databases - whic
Tim,
A should equal 4.242641. Apologies.
VV is double vee.
Marcel,
So when there is any chance that ACOS has to work on any number close to 1,
or -1, a check such as IF VV>1 THEN : VV=1 has to be incorporated on every
occasion?
Takes some of the slickness off the programming.
Colin