Mercurial > octave

comparison NEWS @ 5794:1138ced03f14

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
[project @ 2006-05-08 20:23:04 by jwe]
author jwe
date Mon, 08 May 2006 20:23:07 +0000
parents faafc2d98b8d
children 7e7ed81f5566
comparison
equal deleted inserted replaced
5793:395382df0d8a 5794:1138ced03f14
2 ---------------------------------- 2 ----------------------------------
3 3
4 * Previous versions of Octave had a number of built-in variables to 4 * Previous versions of Octave had a number of built-in variables to
5 control warnings (for example, warn_divide_by_zero). These 5 control warnings (for example, warn_divide_by_zero). These
6 variables have been replaced by warning identifiers that are used 6 variables have been replaced by warning identifiers that are used
7 with the warning function to control the state of warnings. Now, 7 with the warning function to control the state of warnings.
8 instead of writing 8
9 For example, instead of writing
9 10
10 warn_divide_by_zero = false; 11 warn_divide_by_zero = false;
11 12
12 to disable divide-by-zero warnings, you should write 13 to disable divide-by-zero warnings, you should write
13 14
42 using 43 using
43 44
44 help warning_ids 45 help warning_ids
45 46
46 47
48 * All built-in variables have been converted to functions. This
49 change simplifies the interpreter and allows a consistent
50 interface to internal variables for user-defined packages and the
51 core functions distributed with Octave. In most cases, code that
52 simply accesses internal variables does not need to change. Code
53 that sets internal variables will change. For example, instead of
54 writing
55
56 PS1 = ">> ";
57
58 you will need to write
59
60 PS1 (">> ");
61
62
63
47 See NEWS.2 for old news. 64 See NEWS.2 for old news.