looks definitely simpler and more systematic.
I wonder why ominc has chosen the 'exception' for ArcCot.
Is there a difference with special values such as +0, -0, +INF, -INF
or a difference in speed or precision?
- Josef
I suspect you are missing the point here?Josef Templ wrote:looks definitely simpler and more systematic.
I wonder why ominc has chosen the 'exception' for ArcCot.
Is there a difference with special values such as +0, -0, +INF, -INF
or a difference in speed or precision?
π / 2 - ArcTan (0.5) = 1.1071487
ArcTan (1 / 0.5) = 1.1071487
π / 2 - ArcTan (-0.5) = 2.0344439
ArcTan (1 / (-0.5)) = −1.1071487
Robert wrote:These are definitions, not implementation suggestions. Speed and accuracy are not relevant.
Of course they can. And they are probably good suggestions.Josef Templ wrote:The 'definitions' are written in CP syntax.
So why shouldn't that be taken as an implementation suggestion?
Robert wrote:Some diffs for this issue: https://redmine.blackboxframework.org/p ... 0e7fc24030.
IF 10 IN FSWs() THEN FSTPst0; RETURN 0. ELSE END;
YesJosef Templ wrote:[Some Pre/Post conditions are indented some are not.
The BlackBox standard is to not indent them.
Is this because of the missing trap number?
The trap number is usually put to the right of the condition.
I wouldn't introduce new conventions here because of consistency
with the rest of the docu.
Robert wrote:In \\Docu\ Stores the number is to the left. I think this is better, and just assumed that it was the newer convention!
Josef Templ wrote:However, the guidelines in Docu/BB-Docu.odc recommend your version.
But is it really better? I am not sure.
...
Math.Cos.143 Pre: ABS(x) # INF
Math.SinCos.143 Pre: ABS(x) # INF
Math.Tan.143 Pre: ABS(x) # INF
...
SMath.Sin.143 Pre: ABS(x) # INF
SMath.Cos.143 Pre: ABS(x) # INF
SMath.SinCos.143 Pre: ABS(x) # INF
...
Users browsing this forum: No registered users and 1 guest