Mercurial > octave-antonio

comparison doc/interpreter/testfun.txi @ 8481:00df69d7e698

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
[docs] capitalize Octave consistently
author Brian Gough <bjg@gnu.org>
date Tue, 13 Jan 2009 00:25:40 -0500
parents 503001863427
children 03b7f618ab3d
comparison
equal deleted inserted replaced
8480:8ae26422a6ce 8481:00df69d7e698
34 34
35 @DOCSTRING(test) 35 @DOCSTRING(test)
36 36
37 @code{test} scans the named script file looking for lines which 37 @code{test} scans the named script file looking for lines which
38 start with @code{%!}. The prefix is stripped off and the rest of the 38 start with @code{%!}. The prefix is stripped off and the rest of the
39 line is processed through the octave interpreter. If the code 39 line is processed through the Octave interpreter. If the code
40 generates an error, then the test is said to fail. 40 generates an error, then the test is said to fail.
41 41
42 Since @code{eval()} will stop at the first error it encounters, you must 42 Since @code{eval()} will stop at the first error it encounters, you must
43 divide your tests up into blocks, with anything in a separate 43 divide your tests up into blocks, with anything in a separate
44 block evaluated separately. Blocks are introduced by the keyword 44 block evaluated separately. Blocks are introduced by the keyword
283 @end group 283 @end group
284 @end example 284 @end example
285 285
286 but then the code will have to be on the load path and the user 286 but then the code will have to be on the load path and the user
287 will have to remember to type test('name.cc'). Conversely, you 287 will have to remember to type test('name.cc'). Conversely, you
288 can separate the tests from normal octave script files by putting 288 can separate the tests from normal Octave script files by putting
289 them in plain files with no extension rather than in script files. 289 them in plain files with no extension rather than in script files.
290 @c DO I WANT TO INCLUDE THE EDITOR SPECIFIC STATEMENT BELOW??? 290 @c DO I WANT TO INCLUDE THE EDITOR SPECIFIC STATEMENT BELOW???
291 @c Don't forget to tell emacs that the plain text file you are using 291 @c Don't forget to tell emacs that the plain text file you are using
292 @c is actually octave code, using something like: 292 @c is actually octave code, using something like:
293 @c -*-octave-*- 293 @c -*-octave-*-