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
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- Created by GNU Texinfo 6.7, http://www.gnu.org/software/texinfo/ -->
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>Issuing Warnings (GNU Octave (version 6.2.0))</title>
<meta name="description" content="Issuing Warnings (GNU Octave (version 6.2.0))">
<meta name="keywords" content="Issuing Warnings (GNU Octave (version 6.2.0))">
<meta name="resource-type" content="document">
<meta name="distribution" content="global">
<meta name="Generator" content="makeinfo">
<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="Handling-Warnings.html" rel="up" title="Handling Warnings">
<link href="Enabling-and-Disabling-Warnings.html" rel="next" title="Enabling and Disabling Warnings">
<link href="Handling-Warnings.html" rel="prev" title="Handling Warnings">
<style type="text/css">
<!--
a.summary-letter {text-decoration: none}
blockquote.indentedblock {margin-right: 0em}
div.display {margin-left: 3.2em}
div.example {margin-left: 3.2em}
div.lisp {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}
ul.no-bullet {list-style: none}
-->
</style>
<link rel="stylesheet" type="text/css" href="octave.css">
</head>
<body lang="en">
<span id="Issuing-Warnings"></span><div class="header">
<p>
Next: <a href="Enabling-and-Disabling-Warnings.html" accesskey="n" rel="next">Enabling and Disabling Warnings</a>, Up: <a href="Handling-Warnings.html" accesskey="u" rel="up">Handling Warnings</a> [<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="Issuing-Warnings-1"></span><h4 class="subsection">12.2.1 Issuing Warnings</h4>
<p>It is possible to issue warnings from any code using the <code>warning</code>
function. In its most simple form, the <code>warning</code> function takes a
string describing the warning as its input argument. As an example,
the following code controls if the variable ‘<samp>a</samp>’ is non-negative,
and if not issues a warning and sets ‘<samp>a</samp>’ to zero.
</p>
<div class="example">
<pre class="example">a = -1;
if (a < 0)
warning ("'a' must be non-negative. Setting 'a' to zero.");
a = 0;
endif
-| 'a' must be non-negative. Setting 'a' to zero.
</pre></div>
<p>Since warnings aren’t fatal to a running program, it is not possible
to catch a warning using the <code>try</code> statement or something similar.
It is however possible to access the last warning as a string using the
<code>lastwarn</code> function.
</p>
<p>It is also possible to assign an identification string to a warning.
If a warning has such an ID the user can enable and disable this warning
as will be described in the next section. To assign an ID to a warning,
simply call <code>warning</code> with two string arguments, where the first
is the identification string, and the second is the actual warning. Note
that warning IDs are in the format <code>"NAMESPACE:WARNING-NAME"</code>. The
namespace <code>"Octave"</code> is used for Octave’s own warnings. Any other string
is available as a namespace for user’s own warnings.
</p>
<span id="XREFwarning"></span><dl>
<dt id="index-warning">: <em></em> <strong>warning</strong> <em>(<var>template</var>, …)</em></dt>
<dt id="index-warning-1">: <em></em> <strong>warning</strong> <em>(<var>id</var>, <var>template</var>, …)</em></dt>
<dt id="index-warning-2">: <em></em> <strong>warning</strong> <em>("on", <var>id</var>)</em></dt>
<dt id="index-warning-3">: <em></em> <strong>warning</strong> <em>("off", <var>id</var>)</em></dt>
<dt id="index-warning-4">: <em></em> <strong>warning</strong> <em>("error", <var>id</var>)</em></dt>
<dt id="index-warning-5">: <em></em> <strong>warning</strong> <em>("query", <var>id</var>)</em></dt>
<dt id="index-warning-6">: <em></em> <strong>warning</strong> <em>(<var>state</var>, <var>id</var>, "local")</em></dt>
<dt id="index-warning-7">: <em></em> <strong>warning</strong> <em>(<var>warning_struct</var>)</em></dt>
<dt id="index-warning-8">: <em><var>warning_struct</var> =</em> <strong>warning</strong> <em>(…)</em></dt>
<dt id="index-warning-9">: <em></em> <strong>warning</strong> <em>(<var>state</var>, <var>mode</var>)</em></dt>
<dd>
<p>Display a warning message or control the behavior of Octave’s warning system.
</p>
<p>The first call form uses a template <var>template</var> and optional additional
arguments to display a message on the <code>stderr</code> stream. The message is
formatted using the same rules as the <code>printf</code> family of functions
(see <a href="Formatted-Output.html">Formatted Output</a>) and prefixed by the character string
‘<samp>warning: </samp>’<!-- /@w -->. You should use this function when you want to notify the
user of an unusual condition, but only when it makes sense for your program to
go on. For example:
</p>
<div class="example">
<pre class="example">warning ("foo: maybe something wrong here");
</pre></div>
<p>If the warning message does not end with a newline character, Octave will
print a traceback of all the function calls leading to the warning. If the
warning message does end in a newline character, Octave will suppress the
traceback messages as it returns control to the top level. For more details
and examples, see <a href="Raising-Errors.html#XREFerror">error</a>.
</p>
<p>The optional warning identifier <var>id</var> allows users to enable or disable
warnings tagged by this identifier. A message identifier is a string of the
form <code>"NAMESPACE:WARNING-NAME"</code>. Octave’s own warnings use the
<code>"Octave"</code> namespace (see <a href="#XREFwarning_005fids">warning_ids</a>). For
example:
</p>
<div class="example">
<pre class="example">warning ("MyNameSpace:check-something",
"foo: maybe something wrong here");
</pre></div>
<p>The second call form is meant to change and/or query the state of warnings.
The first input argument must be a string <var>state</var> (<code>"on"</code>,
<code>"off"</code>, <code>"error"</code>, or <code>"query"</code>) followed by an optional
warning identifier <var>id</var> or <code>"all"</code> (default).
</p>
<p>The optional output argument <var>warning_struct</var> is a structure or structure
array with fields <code>"state"</code> and <code>"identifier"</code>. The <var>state</var>
argument may have the following values:
</p>
<dl compact="compact">
<dt><code>"on"</code>|<code>"off"</code>:</dt>
<dd><p>Enable or disable the display of warnings identified by <var>id</var> and optionally
return their previous state <var>stout</var>.
</p>
</dd>
<dt><code>"error"</code>:</dt>
<dd><p>Turn warnings identified by <var>id</var> into errors and optionally return their
previous state <var>stout</var>.
</p>
</dd>
<dt><code>"query"</code>:</dt>
<dd><p>Return the current state of warnings identified by <var>id</var>.
</p></dd>
</dl>
<p>A structure or structure array <var>warning_struct</var>, with fields
<code>"state"</code> and <code>"identifier"</code>, may be given as an input to achieve
equivalent results. The following example shows how to temporarily disable a
warning and then restore its original state:
</p>
<div class="example">
<pre class="example">loglog (-1:10);
## Disable the previous warning and save its original state
[~, id] = lastwarn ();
warnstate = warning ("off", id);
loglog (-1:10);
## Restore its original state
warning (warnstate);
</pre></div>
<p>If a final argument <code>"local"</code> is provided then the warning state will be
set temporarily until the end of the current function. Changes to warning
states that are set locally affect the current function and all functions
called from the current scope. The previous warning state is restored on
return from the current function. The <code>"local"</code> option is ignored if
used in the top-level workspace.
</p>
<p>With no input argument <code>warning ()</code> is equivalent to
<code>warning ("query", "all")</code> except that in the absence of an output
argument, the state of warnings is displayed on <code>stderr</code>.
</p>
<p>The level of verbosity of the warning system may also be controlled by two
modes <var>mode</var>:
</p>
<dl compact="compact">
<dt><code>"backtrace"</code>:</dt>
<dd><p>enable/disable the display of the stack trace after the warning message
</p>
</dd>
<dt><code>"verbose"</code>:</dt>
<dd><p>enable/disable the display of additional information after the warning message
</p></dd>
</dl>
<p>In this case the <var>state</var> argument may only be <code>"on"</code> or
<code>"off"</code>.
</p>
<p>Implementation Note: For compatibility with <small>MATLAB</small>, escape sequences in
<var>template</var> (e.g., <code>"\n"</code> => newline) are processed
regardless of whether <var>template</var> has been defined with single quotes, as
long as there are two or more input arguments. To disable escape sequence
expansion use a second backslash before the sequence (e.g.,
<code>"\\n"</code>) or use the
<code>regexptranslate</code> function.
</p>
<p><strong>See also:</strong> <a href="#XREFwarning_005fids">warning_ids</a>, <a href="#XREFlastwarn">lastwarn</a>, <a href="Raising-Errors.html#XREFerror">error</a>.
</p></dd></dl>
<span id="XREFlastwarn"></span><dl>
<dt id="index-lastwarn">: <em>[<var>msg</var>, <var>msgid</var>] =</em> <strong>lastwarn</strong> <em>()</em></dt>
<dt id="index-lastwarn-1">: <em></em> <strong>lastwarn</strong> <em>(<var>msg</var>)</em></dt>
<dt id="index-lastwarn-2">: <em></em> <strong>lastwarn</strong> <em>(<var>msg</var>, <var>msgid</var>)</em></dt>
<dd><p>Query or set the last warning message.
</p>
<p>When called without input arguments, return the last warning message and
message identifier.
</p>
<p>With one argument, set the last warning message to <var>msg</var>.
</p>
<p>With two arguments, also set the last message identifier.
</p>
<p><strong>See also:</strong> <a href="#XREFwarning">warning</a>, <a href="Catching-Errors.html#XREFlasterror">lasterror</a>, <a href="Catching-Errors.html#XREFlasterr">lasterr</a>.
</p></dd></dl>
<p>The functions distributed with Octave can issue one of the following
warnings.
</p>
<span id="XREFwarning_005fids"></span><span id="index-warning-ids"></span>
<dl compact="compact">
<dt><code>Octave:abbreviated-property-match</code></dt>
<dd><p>By default, the <code>Octave:abbreviated-property-match</code> warning is enabled.
</p>
</dd>
<dt><code>Octave:addpath-pkg</code></dt>
<dd><p>If the <code>Octave:addpath-pkg</code> warning is enabled,
Octave will warn when a package directory (i.e., +package_name) is added
to the <code>path</code>. Typically, only the parent directory which contains the
package directory should be added to the load path.
By default, the <code>Octave:addpath-pkg</code> warning is enabled.
</p>
</dd>
<dt><code>Octave:array-as-logical</code></dt>
<dd><p>If the <code>Octave:array-as-logical</code> warning is enabled,
Octave will warn when an array of size greater than 1x1 is used
as a truth value in an if, while, or until statement.
By default, the <code>Octave:array-as-logical</code> warning is disabled.
</p>
</dd>
<dt><code>Octave:array-to-scalar</code></dt>
<dd><p>If the <code>Octave:array-to-scalar</code> warning is enabled, Octave will
warn when an implicit conversion from an array to a scalar value is
attempted.
By default, the <code>Octave:array-to-scalar</code> warning is disabled.
</p>
</dd>
<dt><code>Octave:array-to-vector</code></dt>
<dd><p>If the <code>Octave:array-to-vector</code> warning is enabled, Octave will
warn when an implicit conversion from an array to a vector value is
attempted.
By default, the <code>Octave:array-to-vector</code> warning is disabled.
</p>
</dd>
<dt><code>Octave:assign-as-truth-value</code></dt>
<dd><p>If the <code>Octave:assign-as-truth-value</code> warning is
enabled, a warning is issued for statements like
</p>
<div class="example">
<pre class="example">if (s = t)
…
</pre></div>
<p>since such statements are not common, and it is likely that the intent
was to write
</p>
<div class="example">
<pre class="example">if (s == t)
…
</pre></div>
<p>instead.
</p>
<p>There are times when it is useful to write code that contains
assignments within the condition of a <code>while</code> or <code>if</code>
statement. For example, statements like
</p>
<div class="example">
<pre class="example">while (c = getc ())
…
</pre></div>
<p>are common in C programming.
</p>
<p>It is possible to avoid all warnings about such statements by
disabling the <code>Octave:assign-as-truth-value</code> warning,
but that may also let real errors like
</p>
<div class="example">
<pre class="example">if (x = 1) # intended to test (x == 1)!
…
</pre></div>
<p>slip by.
</p>
<p>In such cases, it is possible suppress errors for specific statements by
writing them with an extra set of parentheses. For example, writing the
previous example as
</p>
<div class="example">
<pre class="example">while ((c = getc ()))
…
</pre></div>
<p>will prevent the warning from being printed for this statement, while
allowing Octave to warn about other assignments used in conditional
contexts.
</p>
<p>By default, the <code>Octave:assign-as-truth-value</code> warning is enabled.
</p>
</dd>
<dt><code>Octave:autoload-relative-file-name</code></dt>
<dd><p>If the <code>Octave:autoload-relative-file-name</code> is enabled,
Octave will warn when parsing autoload() function calls with relative
paths to function files. This usually happens when using autoload()
calls in PKG_ADD files, when the PKG_ADD file is not in the same
directory as the .oct file referred to by the autoload() command.
By default, the <code>Octave:autoload-relative-file-name</code> warning is
enabled.
</p>
</dd>
<dt><code>Octave:built-in-variable-assignment</code></dt>
<dd><p>By default, the <code>Octave:built-in-variable-assignment</code> warning is
enabled.
</p>
</dd>
<dt><code>Octave:classdef-to-struct</code></dt>
<dd><p>If the <code>Octave:classdef-to-struct</code> warning is enabled, a warning
is issued when a classdef object is forcibly converted into a struct with
<code>struct (<var>CLASSDEF_OBJ</var>)</code>. Conversion removes the access
restrictions from the object and makes private and protected properties
visible.
By default, the <code>Octave:classdef-to-struct</code> warning is enabled.
</p>
</dd>
<dt><code>Octave:colon-complex-argument</code></dt>
<dd><p>If the <code>Octave:colon-complex-argument</code> warning is enabled, a warning
is issued when one of the three arguments to the colon operator (base,
increment, limit) is a complex value. For example, <code>1:3*i</code> will
cause a warning to be emitted.
By default, the <code>Octave:colon-complex-argument</code> warning is enabled.
</p>
</dd>
<dt><code>Octave:colon-nonscalar-argument</code></dt>
<dd><p>If the <code>Octave:colon-nonscalar-argument</code> warning is enabled, a warning
is issued when one of the three arguments to the colon operator (base,
increment, limit) is not a scalar. For example, <code>1:[3, 5]</code> will
cause a warning to be emitted.
By default, the <code>Octave:colon-nonscalar-argument</code> warning is enabled.
</p>
</dd>
<dt><code>Octave:data-file-in-path</code></dt>
<dd><p>If the <code>Octave:data-file-in-path</code> warning is enabled, a warning is
issued when Octave does not find the target of a file operation such as
<code>load</code> or <code>fopen</code> directly, but is able to locate the file in
Octave’s search <code>path</code> for files. The warning could indicate that a
different file target than the programmer intended is being used.
By default, the <code>Octave:data-file-in-path</code> warning is enabled.
</p>
</dd>
<dt><code>Octave:deprecated-function</code></dt>
<dd><p>If the <code>Octave:deprecated-function</code> warning is enabled, a
warning is issued when Octave encounters a function that is obsolete and
scheduled for removal from Octave.
By default, the <code>Octave:deprecated-function</code> warning is enabled.
</p>
</dd>
<dt><code>Octave:deprecated-keyword</code></dt>
<dd><p>If the <code>Octave:deprecated-keyword</code> warning is enabled, a
warning is issued when Octave encounters a keyword that is obsolete and
scheduled for removal from Octave.
By default, the <code>Octave:deprecated-keyword</code> warning is enabled.
</p>
</dd>
<dt><code>Octave:deprecated-property</code></dt>
<dd><p>If the <code>Octave:deprecated-property</code> warning is enabled, a
warning is issued when Octave encounters a graphics property that
is obsolete and scheduled for removal from Octave.
By default, the <code>Octave:deprecated-property</code> warning is enabled.
</p>
</dd>
<dt><code>Octave:eigs:UnconvergedEigenvalues</code></dt>
<dd><p>If the <code>Octave:eigs:UnconvergedEigenvalues</code> warning is enabled then
the eigs function will issue a warning if the number of calculated
eigenvalues is less than the number of requested eigenvalues.
By default, the <code>Octave:eigs:UnconvergedEigenvalues</code> warning is
enabled.
</p>
</dd>
<dt><code>Octave:empty-index</code></dt>
<dd><p>If the <code>Octave:empty-index</code> warning is enabled then Octave will emit a
warning whenever indexing operators are used without an index, for example
<code><var>x</var>()</code>.
By default, the <code>Octave:empty-index</code> warning is enabled.
</p>
</dd>
<dt><code>Octave:erase:chararray</code></dt>
<dd><p>If the <code>Octave:erase:chararray</code> warning is enabled then the erase
function will issue a warning if the input pattern is a character array
rather than a string or cell array of strings.
By default, the <code>Octave:erase:chararray</code> warning is enabled.
</p>
</dd>
<dt><code>Octave:function-name-clash</code></dt>
<dd><p>If the <code>Octave:function-name-clash</code> warning is enabled, a
warning is issued when Octave finds that the name of a function
defined in a function file differs from the name of the file. (If
the names disagree, the name declared inside the file is ignored.)
By default, the <code>Octave:function-name-clash</code> warning is enabled.
</p>
</dd>
<dt><code>Octave:future-time-stamp</code></dt>
<dd><p>If the <code>Octave:future-time-stamp</code> warning is enabled, Octave
will print a warning if it finds a function file with a time stamp
that is in the future.
By default, the <code>Octave:future-time-stamp</code> warning is enabled.
</p>
</dd>
<dt><code>Octave:glyph-render</code></dt>
<dd><p>If the <code>Octave:glyph-render</code> warning is enabled, Octave will
print a warning if the glyph for a character couldn’t be rendered with
the current font.
By default, the <code>Octave:glyph-render</code> warning is enabled.
</p>
</dd>
<dt><code>Octave:imag-to-real</code></dt>
<dd><p>If the <code>Octave:imag-to-real</code> warning is enabled, a warning is
printed for implicit conversions of complex numbers to real numbers.
By default, the <code>Octave:imag-to-real</code> warning is disabled.
</p>
</dd>
<dt><code>Octave:language-extension</code></dt>
<dd><p>Print warnings when using features that are unique to the Octave
language and that may still be missing in <small>MATLAB</small>.
By default, the <code>Octave:language-extension</code> warning is disabled.
The <samp>--traditional</samp> or <samp>--braindead</samp> startup options for
Octave may also be of use, see <a href="Command-Line-Options.html">Command Line Options</a>.
</p>
</dd>
<dt><code>Octave:legacy-function</code></dt>
<dd><p>If the <code>Octave:legacy-function</code> warning is enabled, a
warning is issued when Octave encounters a function that <small>MATLAB</small> has
suggested should be avoided. The function may become obsolete at some
point in the future and removed, in which case the warning will change to
<code>Octave:deprecated-function</code>, and the function will continue to exist
for two further versions of Octave before being removed.
By default, the <code>Octave:legacy-function</code> warning is enabled.
</p>
</dd>
<dt><code>Octave:logical-conversion</code></dt>
<dd><p>By default, the <code>Octave:logical-conversion</code> warning is enabled.
</p>
</dd>
<dt><code>Octave:lu:sparse_input</code></dt>
<dd><p>If the <code>Octave:lu:sparse_input</code> warning is enabled, Octave
will warn when the lu function is called with a sparse input and less than
four output arguments. In this case, sparsity-preserving column
permutations are not performed and the result may be inaccurate.
By default, the <code>Octave:lu:sparse_input</code> warning is enabled.
</p>
</dd>
<dt><code>Octave:missing-glyph</code></dt>
<dd><p>If the <code>Octave:glyph-render</code> warning is enabled, Octave will
print a warning if the current font doesn’t provide a glyph for a
used character.
By default, the <code>Octave:missing-glyph</code> warning is enabled.
</p>
</dd>
<dt><code>Octave:missing-semicolon</code></dt>
<dd><p>If the <code>Octave:missing-semicolon</code> warning is enabled, Octave
will warn when statements in function definitions don’t end in
semicolons.
By default the <code>Octave:missing-semicolon</code> warning is disabled.
</p>
</dd>
<dt><code>Octave:mixed-string-concat</code></dt>
<dd><p>If the <code>Octave:mixed-string-concat</code> warning is enabled, print a
warning when concatenating a mixture of double and single quoted strings.
By default, the <code>Octave:mixed-string-concat</code> warning is disabled.
</p>
</dd>
<dt><code>Octave:nearly-singular-matrix</code></dt>
<dt><code>Octave:singular-matrix</code></dt>
<dd><p>These warnings are emitted if a (nearly) singular matrix is inverted.
By default, the <code>Octave:nearly-singular-matrix</code> and
<code>Octave:singular-matrix</code> warnings are enabled.
</p>
</dd>
<dt><code>Octave:neg-dim-as-zero</code></dt>
<dd><p>If the <code>Octave:neg-dim-as-zero</code> warning is enabled, print a warning
for expressions like
</p>
<div class="example">
<pre class="example">eye (-1)
</pre></div>
<p>By default, the <code>Octave:neg-dim-as-zero</code> warning is disabled.
</p>
</dd>
<dt><code>Octave:noninteger-range-as-index</code></dt>
<dd><p>By default, the <code>Octave:noninteger-range-as-index</code> warning is enabled.
</p>
</dd>
<dt><code>Octave:num-to-str</code></dt>
<dd><p>If the <code>Octave:num-to-str</code> warning is enable, a warning is
printed for implicit conversions of numbers to their UTF-8 encoded character
equivalents when strings are constructed using a mixture of strings and
numbers in matrix notation. For example,
</p>
<div class="example">
<pre class="example">[ "f", 111, 111 ]
⇒ "foo"
</pre></div>
<p>elicits a warning if the <code>Octave:num-to-str</code> warning is
enabled. By default, the <code>Octave:num-to-str</code> warning is enabled.
</p>
</dd>
<dt><code>Octave:possible-matlab-short-circuit-operator</code></dt>
<dd><p>If the <code>Octave:possible-matlab-short-circuit-operator</code> warning
is enabled, Octave will warn about using the not short circuiting
operators <code>&</code> and <code>|</code> inside <code>if</code> or <code>while</code>
conditions. They normally never short circuit, but they do short
circuit when used in a condition.
By default, the <code>Octave:possible-matlab-short-circuit-operator</code> warning
is enabled.
</p>
</dd>
<dt><code>Octave:recursive-path-search</code></dt>
<dd><p>If the <code>Octave:recursive-path-search</code> warning is enabled, Octave
will issue a warning if <code>addpath</code> is used with double trailing
slashes.
By default, the <code>Octave:recursive-path-search</code> warning is enabled.
</p>
</dd>
<dt><code>Octave:remove-init-dir</code></dt>
<dd><p>The <code>path</code> function changes the search path that Octave uses
to find functions. It is possible to set the path to a value which
excludes Octave’s own built-in functions. If the
<code>Octave:remove-init-dir</code> warning is enabled then Octave will warn
when the <code>path</code> function has been used in a way that may render
Octave unworkable.
By default, the <code>Octave:remove-init-dir</code> warning is enabled.
</p>
</dd>
<dt><code>Octave:reload-forces-clear</code></dt>
<dd><p>If several functions have been loaded from the same file, Octave must
clear all the functions before any one of them can be reloaded. If
the <code>Octave:reload-forces-clear</code> warning is enabled, Octave will
warn you when this happens, and print a list of the additional
functions that it is forced to clear.
By default, the <code>Octave:reload-forces-clear</code> warning is enabled.
</p>
</dd>
<dt><code>Octave:separator-insert</code></dt>
<dd><p>Print warning if commas or semicolons might be inserted
automatically in literal matrices.
By default, the <code>Octave:separator-insert</code> warning is disabled.
</p>
</dd>
<dt><code>Octave:shadowed-function</code></dt>
<dd><p>If the <code>Octave:shadowed-function</code> warning is enabled, Octave will
warn if a path is added to the search path that contains functions
that shadow core functions.
By default, the <code>Octave:shadowed-function</code> warning is enabled.
</p>
</dd>
<dt><code>Octave:single-quote-string</code></dt>
<dd><p>Print warning if a single quote character is used to introduce a
string constant.
By default, the <code>Octave:single-quote-string</code> warning is disabled.
</p>
</dd>
<dt><code>Octave:sqrtm:SingularMatrix</code></dt>
<dd><p>By default, the <code>Octave:sqrtm:SingularMatrix</code> warning is enabled.
</p>
</dd>
<dt><code>Octave:str-to-num</code></dt>
<dd><p>If the <code>Octave:str-to-num</code> warning is enabled, a warning is printed
for implicit conversions of strings to their numeric UTF-8 encoded byte
sequences. For example,
</p>
<div class="example">
<pre class="example">"abc" + 0
⇒ 97 98 99
</pre></div>
<p>elicits a warning if the <code>Octave:str-to-num</code> warning is enabled.
By default, the <code>Octave:str-to-num</code> warning is disabled.
</p>
</dd>
<dt><code>Octave:text_interpreter</code></dt>
<dd><p>If the <code>Octave:text_interpreter</code> warning is enabled, a warning is
printed when the <code>"interpreter"</code> property of a text graphics object
is set to the unsupported value of <code>"latex"</code>. Even when enabled,
the warning message is printed just once per Octave session.
By default, the <code>Octave:glyph-render</code> warning is enabled.
</p>
</dd>
<dt><code>Octave:variable-switch-label</code></dt>
<dd><p>If the <code>Octave:variable-switch-label</code> warning is enabled, Octave
will print a warning if a switch label is not a constant or constant
expression.
By default, the <code>Octave:variable-switch-label</code> warning is disabled.
</p></dd>
</dl>
<hr>
<div class="header">
<p>
Next: <a href="Enabling-and-Disabling-Warnings.html" accesskey="n" rel="next">Enabling and Disabling Warnings</a>, Up: <a href="Handling-Warnings.html" accesskey="u" rel="up">Handling Warnings</a> [<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>
</body>
</html>
|
