Interval package: Difference between revisions

Jump to navigation Jump to search
253 bytes added ,  28 March 2015
m
→‎Error handling: Added information for fixing the warning reasons
(→‎Error handling: Added warning id interval:NaI)
m (→‎Error handling: Added information for fixing the warning reasons)
Line 302: Line 302:
|-
|-
| interval:ImplicitPromote
| interval:ImplicitPromote
|style="vertical-align:top" | An interval operation has been evaluated on both, a bare and a decorated interval. The bare interval has been converted into a decorated interval in order to produce a decorated result. Note: This warning does not occur if a bare interval literal string gets promoted into a decorated interval, e. g., <code>infsupdec (1, 2) + "[3, 4]"</code> does not produce this warning whereas <code>infsupdec (1, 2) + infsup (3, 4)</code> does.
|style="vertical-align:top" | An interval operation has been evaluated on both, a bare and a decorated interval. The bare interval has been converted into a decorated interval in order to produce a decorated result. Note: This warning does not occur if a bare interval literal string gets promoted into a decorated interval, e. g., <code>infsupdec (1, 2) + "[3, 4]"</code> does not produce this warning whereas <code>infsupdec (1, 2) + infsup (3, 4)</code> does. A bare interval can be explicitly promoted with the newdec [http://octave.sourceforge.net/interval/function/@infsup/newdec.html] function.
|style="vertical-align:top" | The implicit conversion applies the best possible decoration for the bare interval. If the bare interval has been produced from an interval arithmetic computation, this branch of computation is not covered by the decoration information and the final decoration could be considered wrong. For example, <code>infsupdec (1, 2) + infsup (0, 1) ^ 0</code> would ignore that 0<sup>0</sup> is undefined.
|style="vertical-align:top" | The implicit conversion applies the best possible decoration for the bare interval. If the bare interval has been produced from an interval arithmetic computation, this branch of computation is not covered by the decoration information and the final decoration could be considered wrong. For example, <code>infsupdec (1, 2) + infsup (0, 1) ^ 0</code> would ignore that 0<sup>0</sup> is undefined.
|-
|-
Line 310: Line 310:
|-
|-
| interval:NaI
| interval:NaI
|style="vertical-align:top" | An error has occured during interval construction and the NaI object has been produced. The warning text contains further details.
|style="vertical-align:top" | An error has occured during interval construction and the NaI object has been produced. The warning text contains further details. A NaI can be explicitly created with the nai [http://octave.sourceforge.net/interval/function/nai.html] function.
|style="vertical-align:top" | Nothing bad is going to happen, because the semantics of NaI are well defined by IEEE 1788. However, the user might choose to cancel the algorithm immediately when the NaI is encountered for the first time.
|style="vertical-align:top" | Nothing bad is going to happen, because the semantics of NaI are well defined by IEEE 1788. However, the user might choose to cancel the algorithm immediately when the NaI is encountered for the first time.
|}
|}
240

edits

Navigation menu