File: Bug-Criteria.html

package info (click to toggle)
octave 7.3.0-2
  • links: PTS, VCS
  • area: main
  • in suites: bookworm
  • size: 130,464 kB
  • sloc: cpp: 332,823; ansic: 71,320; fortran: 20,963; objc: 8,562; sh: 8,115; yacc: 4,882; lex: 4,438; perl: 1,554; java: 1,366; awk: 1,257; makefile: 652; xml: 173
file content (101 lines) | stat: -rw-r--r-- 4,153 bytes parent folder | download
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
90
91
92
93
94
95
96
97
98
99
100
101
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- Created by GNU Texinfo 6.8, https://www.gnu.org/software/texinfo/ -->
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>Bug Criteria (GNU Octave (version 7.3.0))</title>

<meta name="description" content="Bug Criteria (GNU Octave (version 7.3.0))">
<meta name="keywords" content="Bug Criteria (GNU Octave (version 7.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-anchor {visibility: hidden; text-decoration: none; line-height: 0em}
a.summary-letter {text-decoration: none}
blockquote.indentedblock {margin-right: 0em}
div.display {margin-left: 3.2em}
div.example {margin-left: 3.2em}
kbd {font-style: oblique}
pre.display {font-family: inherit}
pre.format {font-family: inherit}
pre.menu-comment {font-family: serif}
pre.menu-preformatted {font-family: serif}
span.nolinebreak {white-space: nowrap}
span.roman {font-family: initial; font-weight: normal}
span.sansserif {font-family: sans-serif; font-weight: normal}
span:hover a.copiable-anchor {visibility: visible}
ul.no-bullet {list-style: none}
-->
</style>
<link rel="stylesheet" type="text/css" href="octave.css">


</head>

<body lang="en">
<div class="appendixsubsec" id="Bug-Criteria">
<div class="header">
<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>
<span id="Have-You-Found-a-Bug_003f"></span><h4 class="appendixsubsec">D.2.1 Have You Found a Bug?</h4>
<span id="index-bug-criteria"></span>

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

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

</li><li> <span id="index-undefined-behavior"></span>
<span id="index-undefined-function-value"></span>
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> <span id="index-erroneous-messages"></span>
<span id="index-incorrect-error-messages"></span>
<span id="index-error-messages_002c-incorrect"></span>
If Octave produces an error message for valid input, that is a bug.

</li><li> <span id="index-invalid-input"></span>
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> <span id="index-improving-Octave"></span>
<span id="index-suggestions"></span>
If you are an experienced user of programs like Octave, your suggestions
for improvement are welcome in any case.
</li></ul>

</div>



</body>
</html>