File: Bug-Criteria.html

package info (click to toggle)
octave 10.3.0-1
  • links: PTS, VCS
  • area: main
  • in suites:
  • size: 145,388 kB
  • sloc: cpp: 335,976; ansic: 82,241; fortran: 20,963; objc: 9,402; sh: 8,756; yacc: 4,392; lex: 4,333; perl: 1,544; java: 1,366; awk: 1,259; makefile: 659; xml: 192
file content (89 lines) | stat: -rw-r--r-- 3,987 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
<!DOCTYPE html>
<html>
<!-- Created by GNU Texinfo 7.1.1, https://www.gnu.org/software/texinfo/ -->
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>Bug Criteria (GNU Octave (version 10.3.0))</title>

<meta name="description" content="Bug Criteria (GNU Octave (version 10.3.0))">
<meta name="keywords" content="Bug Criteria (GNU Octave (version 10.3.0))">
<meta name="resource-type" content="document">
<meta name="distribution" content="global">
<meta name="Generator" content="makeinfo">
<meta name="viewport" content="width=device-width,initial-scale=1">

<link href="index.html" rel="start" title="Top">
<link href="Concept-Index.html" rel="index" title="Concept Index">
<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
<link href="Reporting-Bugs.html" rel="up" title="Reporting Bugs">
<link href="Bug-Tracker.html" rel="next" title="Bug Tracker">
<style type="text/css">
<!--
a.copiable-link {visibility: hidden; text-decoration: none; line-height: 0em}
span:hover a.copiable-link {visibility: visible}
ul.mark-bullet {list-style-type: disc}
-->
</style>
<link rel="stylesheet" type="text/css" href="octave.css">


</head>

<body lang="en">
<div class="appendixsubsec-level-extent" id="Bug-Criteria">
<div class="nav-panel">
<p>
Next: <a href="Bug-Tracker.html" accesskey="n" rel="next">Where to Report Bugs</a>, Up: <a href="Reporting-Bugs.html" accesskey="u" rel="up">Reporting Bugs</a> &nbsp; [<a href="index.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="Concept-Index.html" title="Index" rel="index">Index</a>]</p>
</div>
<hr>
<h4 class="appendixsubsec" id="Have-You-Found-a-Bug_003f"><span>D.2.1 Have You Found a Bug?<a class="copiable-link" href="#Have-You-Found-a-Bug_003f"> &para;</a></span></h4>
<a class="index-entry-id" id="index-bug-criteria"></a>

<p>If you are not sure whether you have found a bug, here are some guidelines:
</p>
<ul class="itemize mark-bullet">
<li><a class="index-entry-id" id="index-fatal-signal"></a>
<a class="index-entry-id" id="index-core-dump"></a>
If Octave gets a fatal signal, for any input whatever, that is
a bug.  Reliable interpreters never crash.

</li><li><a class="index-entry-id" id="index-incorrect-output"></a>
<a class="index-entry-id" id="index-incorrect-results"></a>
<a class="index-entry-id" id="index-results_002c-incorrect"></a>
<a class="index-entry-id" id="index-answers_002c-incorrect"></a>
<a class="index-entry-id" id="index-erroneous-results"></a>
<a class="index-entry-id" id="index-wrong-answers"></a>
If Octave produces incorrect results, for any input whatever,
that is a bug.

</li><li><a class="index-entry-id" id="index-undefined-behavior"></a>
<a class="index-entry-id" id="index-undefined-function-value"></a>
Some output may appear to be incorrect when it is in fact due to a
program whose behavior is undefined, which happened by chance to give
the desired results on another system.  For example, the range operator
may produce different results because of differences in the way floating
point arithmetic is handled on various systems.

</li><li><a class="index-entry-id" id="index-erroneous-messages"></a>
<a class="index-entry-id" id="index-incorrect-error-messages"></a>
<a class="index-entry-id" id="index-error-messages_002c-incorrect"></a>
If Octave produces an error message for valid input, that is a bug.

</li><li><a class="index-entry-id" id="index-invalid-input"></a>
If Octave does not produce an error message for invalid input, that is
a bug.  However, you should note that your idea of &ldquo;invalid input&rdquo;
might be my idea of &ldquo;an extension&rdquo; or &ldquo;support for traditional
practice&rdquo;.

</li><li><a class="index-entry-id" id="index-improving-Octave"></a>
<a class="index-entry-id" id="index-suggestions"></a>
If you are an experienced user of programs like Octave, your suggestions
for improvement are welcome in any case.
</li></ul>

</div>



</body>
</html>