|
3294
|
1 @c Copyright (C) 1996, 1997 John W. Eaton |
|
|
2 @c This is part of the Octave manual. |
|
|
3 @c For copying conditions, see the file gpl.texi. |
|
|
4 |
|
4167
|
5 @node Functions and Scripts |
|
3294
|
6 @chapter Functions and Script Files |
|
|
7 @cindex defining functions |
|
|
8 @cindex user-defined functions |
|
|
9 @cindex functions, user-defined |
|
|
10 @cindex script files |
|
|
11 |
|
|
12 Complicated Octave programs can often be simplified by defining |
|
|
13 functions. Functions can be defined directly on the command line during |
|
|
14 interactive Octave sessions, or in external files, and can be called just |
|
|
15 like built-in functions. |
|
|
16 |
|
|
17 @menu |
|
|
18 * Defining Functions:: |
|
|
19 * Multiple Return Values:: |
|
|
20 * Variable-length Argument Lists:: |
|
|
21 * Variable-length Return Lists:: |
|
|
22 * Returning From a Function:: |
|
|
23 * Function Files:: |
|
|
24 * Script Files:: |
|
|
25 * Dynamically Linked Functions:: |
|
|
26 * Organization of Functions:: |
|
|
27 @end menu |
|
|
28 |
|
4167
|
29 @node Defining Functions |
|
3294
|
30 @section Defining Functions |
|
|
31 @cindex @code{function} statement |
|
|
32 @cindex @code{endfunction} statement |
|
|
33 |
|
|
34 In its simplest form, the definition of a function named @var{name} |
|
|
35 looks like this: |
|
|
36 |
|
|
37 @example |
|
|
38 @group |
|
|
39 function @var{name} |
|
|
40 @var{body} |
|
|
41 endfunction |
|
|
42 @end group |
|
|
43 @end example |
|
|
44 |
|
|
45 @noindent |
|
|
46 A valid function name is like a valid variable name: a sequence of |
|
|
47 letters, digits and underscores, not starting with a digit. Functions |
|
|
48 share the same pool of names as variables. |
|
|
49 |
|
|
50 The function @var{body} consists of Octave statements. It is the |
|
|
51 most important part of the definition, because it says what the function |
|
|
52 should actually @emph{do}. |
|
|
53 |
|
|
54 For example, here is a function that, when executed, will ring the bell |
|
|
55 on your terminal (assuming that it is possible to do so): |
|
|
56 |
|
|
57 @example |
|
|
58 @group |
|
|
59 function wakeup |
|
|
60 printf ("\a"); |
|
|
61 endfunction |
|
|
62 @end group |
|
|
63 @end example |
|
|
64 |
|
|
65 The @code{printf} statement (@pxref{Input and Output}) simply tells |
|
|
66 Octave to print the string @code{"\a"}. The special character @samp{\a} |
|
|
67 stands for the alert character (ASCII 7). @xref{Strings}. |
|
|
68 |
|
|
69 Once this function is defined, you can ask Octave to evaluate it by |
|
|
70 typing the name of the function. |
|
|
71 |
|
|
72 Normally, you will want to pass some information to the functions you |
|
|
73 define. The syntax for passing parameters to a function in Octave is |
|
|
74 |
|
|
75 @example |
|
|
76 @group |
|
|
77 function @var{name} (@var{arg-list}) |
|
|
78 @var{body} |
|
|
79 endfunction |
|
|
80 @end group |
|
|
81 @end example |
|
|
82 |
|
|
83 @noindent |
|
|
84 where @var{arg-list} is a comma-separated list of the function's |
|
|
85 arguments. When the function is called, the argument names are used to |
|
|
86 hold the argument values given in the call. The list of arguments may |
|
|
87 be empty, in which case this form is equivalent to the one shown above. |
|
|
88 |
|
|
89 To print a message along with ringing the bell, you might modify the |
|
|
90 @code{beep} to look like this: |
|
|
91 |
|
|
92 @example |
|
|
93 @group |
|
|
94 function wakeup (message) |
|
|
95 printf ("\a%s\n", message); |
|
|
96 endfunction |
|
|
97 @end group |
|
|
98 @end example |
|
|
99 |
|
|
100 Calling this function using a statement like this |
|
|
101 |
|
|
102 @example |
|
|
103 wakeup ("Rise and shine!"); |
|
|
104 @end example |
|
|
105 |
|
|
106 @noindent |
|
|
107 will cause Octave to ring your terminal's bell and print the message |
|
|
108 @samp{Rise and shine!}, followed by a newline character (the @samp{\n} |
|
|
109 in the first argument to the @code{printf} statement). |
|
|
110 |
|
|
111 In most cases, you will also want to get some information back from the |
|
|
112 functions you define. Here is the syntax for writing a function that |
|
|
113 returns a single value: |
|
|
114 |
|
|
115 @example |
|
|
116 @group |
|
|
117 function @var{ret-var} = @var{name} (@var{arg-list}) |
|
|
118 @var{body} |
|
|
119 endfunction |
|
|
120 @end group |
|
|
121 @end example |
|
|
122 |
|
|
123 @noindent |
|
|
124 The symbol @var{ret-var} is the name of the variable that will hold the |
|
|
125 value to be returned by the function. This variable must be defined |
|
|
126 before the end of the function body in order for the function to return |
|
|
127 a value. |
|
|
128 |
|
|
129 Variables used in the body of a function are local to the |
|
|
130 function. Variables named in @var{arg-list} and @var{ret-var} are also |
|
|
131 local to the function. @xref{Global Variables}, for information about |
|
|
132 how to access global variables inside a function. |
|
|
133 |
|
|
134 For example, here is a function that computes the average of the |
|
|
135 elements of a vector: |
|
|
136 |
|
|
137 @example |
|
|
138 @group |
|
|
139 function retval = avg (v) |
|
|
140 retval = sum (v) / length (v); |
|
|
141 endfunction |
|
|
142 @end group |
|
|
143 @end example |
|
|
144 |
|
|
145 If we had written @code{avg} like this instead, |
|
|
146 |
|
|
147 @example |
|
|
148 @group |
|
|
149 function retval = avg (v) |
|
4029
|
150 if (isvector (v)) |
|
3294
|
151 retval = sum (v) / length (v); |
|
|
152 endif |
|
|
153 endfunction |
|
|
154 @end group |
|
|
155 @end example |
|
|
156 |
|
|
157 @noindent |
|
|
158 and then called the function with a matrix instead of a vector as the |
|
|
159 argument, Octave would have printed an error message like this: |
|
|
160 |
|
|
161 @example |
|
|
162 @group |
|
|
163 error: `retval' undefined near line 1 column 10 |
|
|
164 error: evaluating index expression near line 7, column 1 |
|
|
165 @end group |
|
|
166 @end example |
|
|
167 |
|
|
168 @noindent |
|
|
169 because the body of the @code{if} statement was never executed, and |
|
|
170 @code{retval} was never defined. To prevent obscure errors like this, |
|
|
171 it is a good idea to always make sure that the return variables will |
|
|
172 always have values, and to produce meaningful error messages when |
|
|
173 problems are encountered. For example, @code{avg} could have been |
|
|
174 written like this: |
|
|
175 |
|
|
176 @example |
|
|
177 @group |
|
|
178 function retval = avg (v) |
|
|
179 retval = 0; |
|
4029
|
180 if (isvector (v)) |
|
3294
|
181 retval = sum (v) / length (v); |
|
|
182 else |
|
|
183 error ("avg: expecting vector argument"); |
|
|
184 endif |
|
|
185 endfunction |
|
|
186 @end group |
|
|
187 @end example |
|
|
188 |
|
|
189 There is still one additional problem with this function. What if it is |
|
|
190 called without an argument? Without additional error checking, Octave |
|
|
191 will probably print an error message that won't really help you track |
|
|
192 down the source of the error. To allow you to catch errors like this, |
|
|
193 Octave provides each function with an automatic variable called |
|
|
194 @code{nargin}. Each time a function is called, @code{nargin} is |
|
|
195 automatically initialized to the number of arguments that have actually |
|
|
196 been passed to the function. For example, we might rewrite the |
|
|
197 @code{avg} function like this: |
|
|
198 |
|
|
199 @example |
|
|
200 @group |
|
|
201 function retval = avg (v) |
|
|
202 retval = 0; |
|
|
203 if (nargin != 1) |
|
|
204 usage ("avg (vector)"); |
|
|
205 endif |
|
4029
|
206 if (isvector (v)) |
|
3294
|
207 retval = sum (v) / length (v); |
|
|
208 else |
|
|
209 error ("avg: expecting vector argument"); |
|
|
210 endif |
|
|
211 endfunction |
|
|
212 @end group |
|
|
213 @end example |
|
|
214 |
|
|
215 Although Octave does not automatically report an error if you call a |
|
|
216 function with more arguments than expected, doing so probably indicates |
|
|
217 that something is wrong. Octave also does not automatically report an |
|
|
218 error if a function is called with too few arguments, but any attempt to |
|
|
219 use a variable that has not been given a value will result in an error. |
|
|
220 To avoid such problems and to provide useful messages, we check for both |
|
|
221 possibilities and issue our own error message. |
|
|
222 |
|
|
223 @defvr {Automatic Variable} nargin |
|
|
224 When a function is called, this local variable is automatically |
|
|
225 initialized to the number of arguments passed to the function. At the |
|
|
226 top level, @code{nargin} holds the number of command line arguments that |
|
|
227 were passed to Octave. |
|
|
228 @end defvr |
|
|
229 |
|
3371
|
230 @DOCSTRING(silent_functions) |
|
3294
|
231 |
|
3371
|
232 @DOCSTRING(warn_missing_semicolon) |
|
3294
|
233 |
|
4167
|
234 @node Multiple Return Values |
|
3294
|
235 @section Multiple Return Values |
|
|
236 |
|
|
237 Unlike many other computer languages, Octave allows you to define |
|
|
238 functions that return more than one value. The syntax for defining |
|
|
239 functions that return multiple values is |
|
|
240 |
|
|
241 @example |
|
|
242 function [@var{ret-list}] = @var{name} (@var{arg-list}) |
|
|
243 @var{body} |
|
|
244 endfunction |
|
|
245 @end example |
|
|
246 |
|
|
247 @noindent |
|
|
248 where @var{name}, @var{arg-list}, and @var{body} have the same meaning |
|
|
249 as before, and @var{ret-list} is a comma-separated list of variable |
|
|
250 names that will hold the values returned from the function. The list of |
|
|
251 return values must have at least one element. If @var{ret-list} has |
|
|
252 only one element, this form of the @code{function} statement is |
|
|
253 equivalent to the form described in the previous section. |
|
|
254 |
|
|
255 Here is an example of a function that returns two values, the maximum |
|
|
256 element of a vector and the index of its first occurrence in the vector. |
|
|
257 |
|
|
258 @example |
|
|
259 @group |
|
|
260 function [max, idx] = vmax (v) |
|
|
261 idx = 1; |
|
|
262 max = v (idx); |
|
|
263 for i = 2:length (v) |
|
|
264 if (v (i) > max) |
|
|
265 max = v (i); |
|
|
266 idx = i; |
|
|
267 endif |
|
|
268 endfor |
|
|
269 endfunction |
|
|
270 @end group |
|
|
271 @end example |
|
|
272 |
|
|
273 In this particular case, the two values could have been returned as |
|
|
274 elements of a single array, but that is not always possible or |
|
|
275 convenient. The values to be returned may not have compatible |
|
|
276 dimensions, and it is often desirable to give the individual return |
|
|
277 values distinct names. |
|
|
278 |
|
|
279 In addition to setting @code{nargin} each time a function is called, |
|
|
280 Octave also automatically initializes @code{nargout} to the number of |
|
|
281 values that are expected to be returned. This allows you to write |
|
|
282 functions that behave differently depending on the number of values that |
|
|
283 the user of the function has requested. The implicit assignment to the |
|
|
284 built-in variable @code{ans} does not figure in the count of output |
|
|
285 arguments, so the value of @code{nargout} may be zero. |
|
|
286 |
|
|
287 The @code{svd} and @code{lu} functions are examples of built-in |
|
|
288 functions that behave differently depending on the value of |
|
|
289 @code{nargout}. |
|
|
290 |
|
|
291 It is possible to write functions that only set some return values. For |
|
|
292 example, calling the function |
|
|
293 |
|
|
294 @example |
|
|
295 function [x, y, z] = f () |
|
|
296 x = 1; |
|
|
297 z = 2; |
|
|
298 endfunction |
|
|
299 @end example |
|
|
300 |
|
|
301 @noindent |
|
|
302 as |
|
|
303 |
|
|
304 @example |
|
|
305 [a, b, c] = f () |
|
|
306 @end example |
|
|
307 |
|
|
308 @noindent |
|
|
309 produces: |
|
|
310 |
|
|
311 @example |
|
|
312 a = 1 |
|
|
313 |
|
|
314 b = [](0x0) |
|
|
315 |
|
|
316 c = 2 |
|
|
317 @end example |
|
|
318 |
|
|
319 @noindent |
|
4466
|
320 along with a warning if the value of the built-in variable |
|
|
321 @code{warn_undefined_return_values} is nonzero. |
|
3294
|
322 |
|
|
323 @defvr {Automatic Variable} nargout |
|
|
324 When a function is called, this local variable is automatically |
|
|
325 initialized to the number of arguments expected to be returned. For |
|
|
326 example, |
|
|
327 |
|
|
328 @example |
|
|
329 f () |
|
|
330 @end example |
|
|
331 |
|
|
332 @noindent |
|
|
333 will result in @code{nargout} being set to 0 inside the function |
|
|
334 @code{f} and |
|
|
335 |
|
|
336 @example |
|
|
337 [s, t] = f () |
|
|
338 @end example |
|
|
339 |
|
|
340 @noindent |
|
|
341 will result in @code{nargout} being set to 2 inside the function |
|
|
342 @code{f}. |
|
|
343 |
|
|
344 At the top level, @code{nargout} is undefined. |
|
|
345 @end defvr |
|
|
346 |
|
4466
|
347 @DOCSTRING(warn_undefined_return_values) |
|
3294
|
348 |
|
3371
|
349 @DOCSTRING(nargchk) |
|
3294
|
350 |
|
4167
|
351 @node Variable-length Argument Lists |
|
3294
|
352 @section Variable-length Argument Lists |
|
|
353 @cindex Variable-length argument lists |
|
|
354 @cindex @code{...} |
|
|
355 |
|
|
356 Octave has a real mechanism for handling functions that take an |
|
|
357 unspecified number of arguments, so it is not necessary to place an |
|
|
358 upper bound on the number of optional arguments that a function can |
|
|
359 accept. |
|
|
360 |
|
|
361 @c XXX FIXME XXX -- should we add a note about why this feature is not |
|
|
362 @c compatible with Matlab 5? |
|
|
363 |
|
|
364 Here is an example of a function that uses the new syntax to print a |
|
|
365 header followed by an unspecified number of values: |
|
|
366 |
|
|
367 @example |
|
|
368 function foo (heading, ...) |
|
|
369 disp (heading); |
|
|
370 va_start (); |
|
|
371 ## Pre-decrement to skip `heading' arg. |
|
|
372 while (--nargin) |
|
|
373 disp (va_arg ()); |
|
|
374 endwhile |
|
|
375 endfunction |
|
|
376 @end example |
|
|
377 |
|
|
378 The ellipsis that marks the variable argument list may only appear once |
|
|
379 and must be the last element in the list of arguments. |
|
|
380 |
|
3371
|
381 @DOCSTRING(va_arg) |
|
3294
|
382 |
|
3371
|
383 @DOCSTRING(va_start) |
|
3294
|
384 |
|
|
385 Sometimes it is useful to be able to pass all unnamed arguments to |
|
|
386 another function. The keyword @var{all_va_args} makes this very easy to |
|
|
387 do. For example, |
|
|
388 |
|
|
389 @example |
|
|
390 @group |
|
|
391 function f (...) |
|
|
392 while (nargin--) |
|
|
393 disp (va_arg ()) |
|
|
394 endwhile |
|
|
395 endfunction |
|
|
396 |
|
|
397 function g (...) |
|
|
398 f ("begin", all_va_args, "end") |
|
|
399 endfunction |
|
|
400 |
|
|
401 g (1, 2, 3) |
|
|
402 |
|
|
403 @print{} begin |
|
|
404 @print{} 1 |
|
|
405 @print{} 2 |
|
|
406 @print{} 3 |
|
|
407 @print{} end |
|
|
408 @end group |
|
|
409 @end example |
|
|
410 |
|
|
411 @defvr {Keyword} all_va_args |
|
|
412 This keyword stands for the entire list of optional argument, so it is |
|
|
413 possible to use it more than once within the same function without |
|
|
414 having to call @code{va_start}. It can only be used within functions |
|
|
415 that take a variable number of arguments. It is an error to use it in |
|
|
416 other contexts. |
|
|
417 @end defvr |
|
|
418 |
|
4167
|
419 @node Variable-length Return Lists |
|
3294
|
420 @section Variable-length Return Lists |
|
|
421 @cindex Variable-length return lists |
|
|
422 @cindex @code{...} |
|
|
423 |
|
|
424 Octave also has a real mechanism for handling functions that return an |
|
|
425 unspecified number of values, so it is no longer necessary to place an |
|
|
426 upper bound on the number of outputs that a function can produce. |
|
|
427 |
|
|
428 Here is an example of a function that uses a variable-length return list |
|
|
429 to produce @var{n} values: |
|
|
430 |
|
|
431 @example |
|
|
432 @group |
|
|
433 function [...] = f (n, x) |
|
|
434 for i = 1:n |
|
|
435 vr_val (i * x); |
|
|
436 endfor |
|
|
437 endfunction |
|
|
438 |
|
|
439 [dos, quatro] = f (2, 2) |
|
|
440 @result{} dos = 2 |
|
|
441 @result{} quatro = 4 |
|
|
442 @end group |
|
|
443 @end example |
|
|
444 |
|
|
445 As with variable argument lists, the ellipsis that marks the variable |
|
|
446 return list may only appear once and must be the last element in the |
|
|
447 list of returned values. |
|
|
448 |
|
3371
|
449 @DOCSTRING(vr_val) |
|
3294
|
450 |
|
4167
|
451 @node Returning From a Function |
|
3294
|
452 @section Returning From a Function |
|
|
453 |
|
|
454 The body of a user-defined function can contain a @code{return} statement. |
|
|
455 This statement returns control to the rest of the Octave program. It |
|
|
456 looks like this: |
|
|
457 |
|
|
458 @example |
|
|
459 return |
|
|
460 @end example |
|
|
461 |
|
|
462 Unlike the @code{return} statement in C, Octave's @code{return} |
|
|
463 statement cannot be used to return a value from a function. Instead, |
|
|
464 you must assign values to the list of return variables that are part of |
|
|
465 the @code{function} statement. The @code{return} statement simply makes |
|
|
466 it easier to exit a function from a deeply nested loop or conditional |
|
|
467 statement. |
|
|
468 |
|
|
469 Here is an example of a function that checks to see if any elements of a |
|
|
470 vector are nonzero. |
|
|
471 |
|
|
472 @example |
|
|
473 @group |
|
|
474 function retval = any_nonzero (v) |
|
|
475 retval = 0; |
|
|
476 for i = 1:length (v) |
|
|
477 if (v (i) != 0) |
|
|
478 retval = 1; |
|
|
479 return; |
|
|
480 endif |
|
|
481 endfor |
|
|
482 printf ("no nonzero elements found\n"); |
|
|
483 endfunction |
|
|
484 @end group |
|
|
485 @end example |
|
|
486 |
|
|
487 Note that this function could not have been written using the |
|
|
488 @code{break} statement to exit the loop once a nonzero value is found |
|
|
489 without adding extra logic to avoid printing the message if the vector |
|
|
490 does contain a nonzero element. |
|
|
491 |
|
|
492 @defvr {Keyword} return |
|
|
493 When Octave encounters the keyword @code{return} inside a function or |
|
|
494 script, it returns control to be caller immediately. At the top level, |
|
|
495 the return statement is ignored. A @code{return} statement is assumed |
|
|
496 at the end of every function definition. |
|
|
497 @end defvr |
|
|
498 |
|
3371
|
499 @DOCSTRING(return_last_computed_value) |
|
3294
|
500 |
|
4167
|
501 @node Function Files |
|
3294
|
502 @section Function Files |
|
|
503 @cindex function file |
|
|
504 |
|
|
505 Except for simple one-shot programs, it is not practical to have to |
|
|
506 define all the functions you need each time you need them. Instead, you |
|
|
507 will normally want to save them in a file so that you can easily edit |
|
|
508 them, and save them for use at a later time. |
|
|
509 |
|
|
510 Octave does not require you to load function definitions from files |
|
|
511 before using them. You simply need to put the function definitions in a |
|
|
512 place where Octave can find them. |
|
|
513 |
|
|
514 When Octave encounters an identifier that is undefined, it first looks |
|
|
515 for variables or functions that are already compiled and currently |
|
|
516 listed in its symbol table. If it fails to find a definition there, it |
|
|
517 searches the list of directories specified by the built-in variable |
|
|
518 @code{LOADPATH} for files ending in @file{.m} that have the same base |
|
|
519 name as the undefined identifier.@footnote{The @samp{.m} suffix was |
|
|
520 chosen for compatibility with @sc{Matlab}.} Once Octave finds a file |
|
|
521 with a name that matches, the contents of the file are read. If it |
|
|
522 defines a @emph{single} function, it is compiled and executed. |
|
|
523 @xref{Script Files}, for more information about how you can define more |
|
|
524 than one function in a single file. |
|
|
525 |
|
|
526 When Octave defines a function from a function file, it saves the full |
|
|
527 name of the file it read and the time stamp on the file. After |
|
|
528 that, it checks the time stamp on the file every time it needs the |
|
|
529 function. If the time stamp indicates that the file has changed since |
|
|
530 the last time it was read, Octave reads it again. |
|
|
531 |
|
|
532 Checking the time stamp allows you to edit the definition of a function |
|
|
533 while Octave is running, and automatically use the new function |
|
|
534 definition without having to restart your Octave session. Checking the |
|
|
535 time stamp every time a function is used is rather inefficient, but it |
|
|
536 has to be done to ensure that the correct function definition is used. |
|
|
537 |
|
|
538 To avoid degrading performance unnecessarily by checking the time stamps |
|
|
539 on functions that are not likely to change, Octave assumes that function |
|
|
540 files in the directory tree |
|
|
541 @file{@var{octave-home}/share/octave/@var{version}/m} |
|
|
542 will not change, so it doesn't have to check their time stamps every time the |
|
|
543 functions defined in those files are used. This is normally a very good |
|
|
544 assumption and provides a significant improvement in performance for the |
|
|
545 function files that are distributed with Octave. |
|
|
546 |
|
|
547 If you know that your own function files will not change while you are |
|
|
548 running Octave, you can improve performance by setting the variable |
|
|
549 @code{ignore_function_time_stamp} to @code{"all"}, so that Octave will |
|
|
550 ignore the time stamps for all function files. Setting it to |
|
|
551 @code{"system"} gives the default behavior. If you set it to anything |
|
|
552 else, Octave will check the time stamps on all function files. |
|
|
553 |
|
|
554 @c XXX FIXME XXX -- note about time stamps on files in NFS environments? |
|
|
555 |
|
3371
|
556 @DOCSTRING(DEFAULT_LOADPATH) |
|
3294
|
557 |
|
3371
|
558 @DOCSTRING(LOADPATH) |
|
3294
|
559 |
|
3428
|
560 @DOCSTRING(rehash) |
|
|
561 |
|
|
562 @DOCSTRING(file_in_loadpath) |
|
|
563 |
|
3371
|
564 @DOCSTRING(ignore_function_time_stamp) |
|
3294
|
565 |
|
3371
|
566 @DOCSTRING(warn_function_name_clash) |
|
3294
|
567 |
|
3428
|
568 @DOCSTRING(warn_future_time_stamp) |
|
|
569 |
|
4167
|
570 @node Script Files |
|
3294
|
571 @section Script Files |
|
|
572 |
|
|
573 A script file is a file containing (almost) any sequence of Octave |
|
|
574 commands. It is read and evaluated just as if you had typed each |
|
|
575 command at the Octave prompt, and provides a convenient way to perform a |
|
|
576 sequence of commands that do not logically belong inside a function. |
|
|
577 |
|
|
578 Unlike a function file, a script file must @emph{not} begin with the |
|
|
579 keyword @code{function}. If it does, Octave will assume that it is a |
|
|
580 function file, and that it defines a single function that should be |
|
|
581 evaluated as soon as it is defined. |
|
|
582 |
|
|
583 A script file also differs from a function file in that the variables |
|
|
584 named in a script file are not local variables, but are in the same |
|
|
585 scope as the other variables that are visible on the command line. |
|
|
586 |
|
|
587 Even though a script file may not begin with the @code{function} |
|
|
588 keyword, it is possible to define more than one function in a single |
|
|
589 script file and load (but not execute) all of them at once. To do |
|
|
590 this, the first token in the file (ignoring comments and other white |
|
|
591 space) must be something other than @code{function}. If you have no |
|
|
592 other statements to evaluate, you can use a statement that has no |
|
|
593 effect, like this: |
|
|
594 |
|
|
595 @example |
|
|
596 @group |
|
|
597 # Prevent Octave from thinking that this |
|
|
598 # is a function file: |
|
|
599 |
|
|
600 1; |
|
|
601 |
|
|
602 # Define function one: |
|
|
603 |
|
|
604 function one () |
|
|
605 ... |
|
|
606 @end group |
|
|
607 @end example |
|
|
608 |
|
|
609 To have Octave read and compile these functions into an internal form, |
|
|
610 you need to make sure that the file is in Octave's @code{LOADPATH}, then |
|
|
611 simply type the base name of the file that contains the commands. |
|
|
612 (Octave uses the same rules to search for script files as it does to |
|
|
613 search for function files.) |
|
|
614 |
|
|
615 If the first token in a file (ignoring comments) is @code{function}, |
|
|
616 Octave will compile the function and try to execute it, printing a |
|
|
617 message warning about any non-whitespace characters that appear after |
|
|
618 the function definition. |
|
|
619 |
|
|
620 Note that Octave does not try to look up the definition of any identifier |
|
|
621 until it needs to evaluate it. This means that Octave will compile the |
|
|
622 following statements if they appear in a script file, or are typed at |
|
|
623 the command line, |
|
|
624 |
|
|
625 @example |
|
|
626 @group |
|
|
627 # not a function file: |
|
|
628 1; |
|
|
629 function foo () |
|
|
630 do_something (); |
|
|
631 endfunction |
|
|
632 function do_something () |
|
|
633 do_something_else (); |
|
|
634 endfunction |
|
|
635 @end group |
|
|
636 @end example |
|
|
637 |
|
|
638 @noindent |
|
|
639 even though the function @code{do_something} is not defined before it is |
|
|
640 referenced in the function @code{foo}. This is not an error because |
|
|
641 Octave does not need to resolve all symbols that are referenced by a |
|
|
642 function until the function is actually evaluated. |
|
|
643 |
|
|
644 Since Octave doesn't look for definitions until they are needed, the |
|
|
645 following code will always print @samp{bar = 3} whether it is typed |
|
|
646 directly on the command line, read from a script file, or is part of a |
|
|
647 function body, even if there is a function or script file called |
|
|
648 @file{bar.m} in Octave's @code{LOADPATH}. |
|
|
649 |
|
|
650 @example |
|
|
651 @group |
|
|
652 eval ("bar = 3"); |
|
|
653 bar |
|
|
654 @end group |
|
|
655 @end example |
|
|
656 |
|
|
657 Code like this appearing within a function body could fool Octave if |
|
|
658 definitions were resolved as the function was being compiled. It would |
|
|
659 be virtually impossible to make Octave clever enough to evaluate this |
|
|
660 code in a consistent fashion. The parser would have to be able to |
|
|
661 perform the call to @code{eval} at compile time, and that would be |
|
|
662 impossible unless all the references in the string to be evaluated could |
|
|
663 also be resolved, and requiring that would be too restrictive (the |
|
|
664 string might come from user input, or depend on things that are not |
|
|
665 known until the function is evaluated). |
|
|
666 |
|
|
667 Although Octave normally executes commands from script files that have |
|
|
668 the name @file{@var{file}.m}, you can use the function @code{source} to |
|
|
669 execute commands from any file. |
|
|
670 |
|
3371
|
671 @DOCSTRING(source) |
|
3294
|
672 |
|
4167
|
673 @node Dynamically Linked Functions |
|
3294
|
674 @section Dynamically Linked Functions |
|
|
675 @cindex dynamic linking |
|
|
676 |
|
|
677 On some systems, Octave can dynamically load and execute functions |
|
|
678 written in C++. Octave can only directly call functions written in C++, |
|
|
679 but you can also load functions written in other languages |
|
|
680 by calling them from a simple wrapper function written in C++. |
|
|
681 |
|
|
682 Here is an example of how to write a C++ function that Octave can load, |
|
|
683 with commentary. The source for this function is included in the source |
|
|
684 distributions of Octave, in the file @file{examples/oregonator.cc}. It |
|
|
685 defines the same set of differential equations that are used in the |
|
|
686 example problem of @ref{Ordinary Differential Equations}. By running |
|
|
687 that example and this one, we can compare the execution times to see |
|
|
688 what sort of increase in speed you can expect by using dynamically |
|
|
689 linked functions. |
|
|
690 |
|
|
691 The function defined in @file{oregonator.cc} contains just 8 statements, |
|
|
692 and is not much different than the code defined in the corresponding |
|
|
693 M-file (also distributed with Octave in the file |
|
|
694 @file{examples/oregonator.m}). |
|
|
695 |
|
|
696 Here is the complete text of @file{oregonator.cc}: |
|
|
697 |
|
|
698 just |
|
|
699 |
|
|
700 @example |
|
|
701 @group |
|
|
702 #include <octave/oct.h> |
|
|
703 |
|
|
704 DEFUN_DLD (oregonator, args, , |
|
|
705 "The `oregonator'.") |
|
|
706 @{ |
|
|
707 ColumnVector dx (3); |
|
|
708 |
|
3760
|
709 ColumnVector x (args(0).vector_value ()); |
|
3294
|
710 |
|
|
711 dx(0) = 77.27 * (x(1) - x(0)*x(1) + x(0) |
|
|
712 - 8.375e-06*pow (x(0), 2)); |
|
|
713 |
|
|
714 dx(1) = (x(2) - x(0)*x(1) - x(1)) / 77.27; |
|
|
715 |
|
|
716 dx(2) = 0.161*(x(0) - x(2)); |
|
|
717 |
|
|
718 return octave_value (dx); |
|
|
719 @} |
|
|
720 @end group |
|
|
721 @end example |
|
|
722 |
|
|
723 The first line of the file, |
|
|
724 |
|
|
725 @example |
|
|
726 #include <octave/oct.h> |
|
|
727 @end example |
|
|
728 |
|
|
729 @noindent |
|
|
730 includes declarations for all of Octave's internal functions that you |
|
|
731 will need. If you need other functions from the standard C++ or C |
|
|
732 libraries, you can include the necessary headers here. |
|
|
733 |
|
|
734 The next two lines |
|
|
735 @example |
|
|
736 @group |
|
|
737 DEFUN_DLD (oregonator, args, , |
|
|
738 "The `oregonator'.") |
|
|
739 @end group |
|
|
740 @end example |
|
|
741 |
|
|
742 @noindent |
|
|
743 declares the function. The macro @code{DEFUN_DLD} and the macros that |
|
|
744 it depends on are defined in the files @file{defun-dld.h}, |
|
|
745 @file{defun.h}, and @file{defun-int.h} (these files are included in the |
|
|
746 header file @file{octave/oct.h}). |
|
|
747 |
|
|
748 Note that the third parameter to @code{DEFUN_DLD} (@code{nargout}) is |
|
3686
|
749 not used, so it is omitted from the list of arguments in order to |
|
|
750 avoid the warning from gcc about an unused function parameter. |
|
|
751 |
|
|
752 The next line, |
|
|
753 |
|
|
754 @example |
|
|
755 ColumnVector dx (3); |
|
|
756 @end example |
|
3294
|
757 |
|
|
758 @noindent |
|
|
759 simply declares an object to store the right hand sides of the |
|
3686
|
760 differential equation, and the statement |
|
3294
|
761 |
|
|
762 @example |
|
3760
|
763 ColumnVector x (args(0).vector_value ()); |
|
3294
|
764 @end example |
|
|
765 |
|
|
766 @noindent |
|
3760
|
767 extracts a vector from the first input argument. The |
|
|
768 @code{vector_value} method is used so that the user of the function |
|
|
769 can pass either a row or column vector. The @code{ColumnVector} |
|
|
770 constructor is needed because the ODE class requires a column |
|
|
771 vector. The variable @code{args} is passed to functions defined with |
|
|
772 @code{DEFUN_DLD} as an @code{octave_value_list} object, which includes |
|
|
773 methods for getting the length of the list and extracting individual |
|
|
774 elements. |
|
3294
|
775 |
|
|
776 In this example, we don't check for errors, but that is not difficult. |
|
|
777 All of the Octave's built-in functions do some form of checking on their |
|
|
778 arguments, so you can check the source code for those functions for |
|
|
779 examples of various strategies for verifying that the correct number and |
|
|
780 types of arguments have been supplied. |
|
|
781 |
|
|
782 The next statements |
|
|
783 |
|
|
784 @example |
|
|
785 @group |
|
|
786 ColumnVector dx (3); |
|
|
787 |
|
|
788 dx(0) = 77.27 * (x(1) - x(0)*x(1) + x(0) |
|
|
789 - 8.375e-06*pow (x(0), 2)); |
|
|
790 |
|
|
791 dx(1) = (x(2) - x(0)*x(1) - x(1)) / 77.27; |
|
|
792 |
|
|
793 dx(2) = 0.161*(x(0) - x(2)); |
|
|
794 @end group |
|
|
795 @end example |
|
|
796 |
|
|
797 @noindent |
|
|
798 define the right hand side of the differential equation. Finally, we |
|
|
799 can return @code{dx}: |
|
|
800 |
|
|
801 @example |
|
|
802 return octave_value (dx); |
|
|
803 @end example |
|
|
804 |
|
|
805 @noindent |
|
|
806 The actual return type is @code{octave_value_list}, but it is only |
|
|
807 necessary to convert the return type to an @code{octave_value} because |
|
|
808 there is a default constructor that can automatically create an object |
|
|
809 of that type from an @code{octave_value} object, so we can just use that |
|
|
810 instead. |
|
|
811 |
|
|
812 To use this file, your version of Octave must support dynamic linking. |
|
|
813 To find out if it does, type the command |
|
|
814 @kbd{octave_config_info ("dld")} at the Octave prompt. Support for |
|
|
815 dynamic linking is included if this command returns 1. |
|
|
816 |
|
|
817 To compile the example file, type the command @samp{mkoctfile |
|
|
818 oregonator.cc} at the shell prompt. The script @code{mkoctfile} should |
|
|
819 have been installed along with Octave. Running it will create a file |
|
|
820 called @file{oregonator.oct} that can be loaded by Octave. To test the |
|
|
821 @file{oregonator.oct} file, start Octave and type the command |
|
|
822 |
|
|
823 @example |
|
|
824 oregonator ([1, 2, 3], 0) |
|
|
825 @end example |
|
|
826 |
|
|
827 @noindent |
|
|
828 at the Octave prompt. Octave should respond by printing |
|
|
829 |
|
|
830 @example |
|
|
831 @group |
|
|
832 ans = |
|
|
833 |
|
|
834 77.269353 |
|
|
835 -0.012942 |
|
|
836 -0.322000 |
|
|
837 @end group |
|
|
838 @end example |
|
|
839 |
|
|
840 You can now use the @file{oregonator.oct} file just as you would the |
|
|
841 @code{oregonator.m} file to solve the set of differential equations. |
|
|
842 |
|
|
843 On a 133 MHz Pentium running Linux, Octave can solve the problem shown |
|
3402
|
844 in @ref{Ordinary Differential Equations}, in about 1.4 seconds using the |
|
3294
|
845 dynamically linked function, compared to about 19 seconds using the |
|
|
846 M-file. Similar decreases in execution time can be expected for other |
|
|
847 functions, particularly those that rely on functions like @code{lsode} |
|
|
848 that require user-supplied functions. |
|
|
849 |
|
3428
|
850 Just as for M-files, Octave will automatically reload a dynamically linked |
|
|
851 function when the file that defines it is more recent than the last |
|
|
852 time that the function was loaded. If more than one function is defined |
|
|
853 in a single @file{.oct} file, reloading the file may force other |
|
|
854 functions to be cleared and reloaded. If all the functions loaded from |
|
|
855 a given @file{.oct} file are cleared, Octave will automatically unload |
|
|
856 the @file{.oct} file. |
|
3294
|
857 |
|
3371
|
858 @DOCSTRING(warn_reload_forces_clear) |
|
3294
|
859 |
|
3428
|
860 @c XXX FIXME XXX -- is there a better place for this? |
|
|
861 |
|
|
862 @DOCSTRING(variables_can_hide_functions) |
|
|
863 |
|
3294
|
864 Additional examples for writing dynamically linked functions are |
|
|
865 available in the files in the @file{src} directory of the Octave |
|
|
866 distribution. Currently, this includes the files |
|
|
867 |
|
|
868 @example |
|
|
869 @group |
|
|
870 balance.cc fft2.cc inv.cc qzval.cc |
|
|
871 chol.cc filter.cc log.cc schur.cc |
|
|
872 colloc.cc find.cc lsode.cc sort.cc |
|
|
873 dassl.cc fsolve.cc lu.cc svd.cc |
|
|
874 det.cc givens.cc minmax.cc syl.cc |
|
|
875 eig.cc hess.cc pinv.cc |
|
|
876 expm.cc ifft.cc qr.cc |
|
|
877 fft.cc ifft2.cc quad.cc |
|
|
878 @end group |
|
|
879 @end example |
|
|
880 |
|
|
881 @noindent |
|
|
882 These files use the macro @code{DEFUN_DLD_BUILTIN} instead of |
|
|
883 @code{DEFUN_DLD}. The difference between these two macros is just that |
|
|
884 @code{DEFUN_DLD_BUILTIN} can define a built-in function that is not |
|
|
885 dynamically loaded if the operating system does not support dynamic |
|
|
886 linking. To define your own dynamically linked functions you should use |
|
|
887 @code{DEFUN_DLD}. |
|
|
888 |
|
|
889 There is currently no detailed description of all the functions that you |
|
|
890 can call in a built-in function. For the time being, you will have to |
|
|
891 read the source code for Octave. |
|
|
892 |
|
4167
|
893 @node Organization of Functions |
|
3294
|
894 @section Organization of Functions Distributed with Octave |
|
|
895 |
|
|
896 Many of Octave's standard functions are distributed as function files. |
|
|
897 They are loosely organized by topic, in subdirectories of |
|
|
898 @file{@var{octave-home}/lib/octave/@var{version}/m}, to make it easier |
|
|
899 to find them. |
|
|
900 |
|
|
901 The following is a list of all the function file subdirectories, and the |
|
|
902 types of functions you will find there. |
|
|
903 |
|
|
904 @table @file |
|
|
905 @item audio |
|
|
906 Functions for playing and recording sounds. |
|
|
907 |
|
|
908 @item control |
|
|
909 Functions for design and simulation of automatic control systems. |
|
|
910 |
|
|
911 @item elfun |
|
|
912 Elementary functions. |
|
|
913 |
|
|
914 @item general |
|
|
915 Miscellaneous matrix manipulations, like @code{flipud}, @code{rot90}, |
|
|
916 and @code{triu}, as well as other basic functions, like |
|
4029
|
917 @code{ismatrix}, @code{nargchk}, etc. |
|
3294
|
918 |
|
|
919 @item image |
|
|
920 Image processing tools. These functions require the X Window System. |
|
|
921 |
|
|
922 @item io |
|
|
923 Input-ouput functions. |
|
|
924 |
|
|
925 @item linear-algebra |
|
|
926 Functions for linear algebra. |
|
|
927 |
|
|
928 @item miscellaneous |
|
|
929 Functions that don't really belong anywhere else. |
|
|
930 |
|
|
931 @item plot |
|
|
932 A set of functions that implement the @sc{Matlab}-like plotting functions. |
|
|
933 |
|
|
934 @item polynomial |
|
|
935 Functions for manipulating polynomials. |
|
|
936 |
|
|
937 @item set |
|
|
938 Functions for creating and manipulating sets of unique values. |
|
|
939 |
|
|
940 @item signal |
|
|
941 Functions for signal processing applications. |
|
|
942 |
|
|
943 @item specfun |
|
|
944 Special functions. |
|
|
945 |
|
|
946 @item special-matrix |
|
|
947 Functions that create special matrix forms. |
|
|
948 |
|
|
949 @item startup |
|
|
950 Octave's system-wide startup file. |
|
|
951 |
|
|
952 @item statistics |
|
|
953 Statistical functions. |
|
|
954 |
|
|
955 @item strings |
|
|
956 Miscellaneous string-handling functions. |
|
|
957 |
|
|
958 @item time |
|
|
959 Functions related to time keeping. |
|
|
960 @end table |
