File: octave_8.html

package info (click to toggle)
octave 2.0.16-2
links: PTS
area: main
in suites: potato
size: 26,276 kB
ctags: 16,450
sloc: cpp: 67,548; fortran: 41,514; ansic: 26,682; sh: 7,361; makefile: 4,077; lex: 2,008; yacc: 1,849; lisp: 1,702; perl: 1,676; exp: 123
file content (866 lines) | stat: -rw-r--r-- 21,735 bytes
<HTML>
<HEAD>
<!-- This HTML file has been created by texi2html 1.51
     from ./octave.texi on 18 June 1999 -->

<TITLE>GNU Octave - Variables</TITLE>
</HEAD>
<BODY>
Go to the <A HREF="octave_1.html">first</A>, <A HREF="octave_7.html">previous</A>, <A HREF="octave_9.html">next</A>, <A HREF="octave_40.html">last</A> section, <A HREF="octave_toc.html">table of contents</A>.
<P><HR><P>


<H1><A NAME="SEC59" HREF="octave_toc.html#TOC59">Variables</A></H1>
<P>
<A NAME="IDX213"></A>
<A NAME="IDX214"></A>

</P>
<P>
Variables let you give names to values and refer to them later.  You have
already seen variables in many of the examples.  The name of a variable
must be a sequence of letters, digits and underscores, but it may not begin
with a digit.  Octave does not enforce a limit on the length of variable
names, but it is seldom useful to have variables with names longer than
about 30 characters.  The following are all valid variable names

</P>
<P>
<A NAME="IDX215"></A>
<A NAME="IDX216"></A>
<A NAME="IDX217"></A>

<PRE>
x
x15
__foo_bar_baz__
fucnrdthsucngtagdjb
</PRE>

<P>
However, names like <CODE>__foo_bar_baz__</CODE> that begin and end with two
underscores are understood to be reserved for internal use by Octave.
You should not use them in code you write, except to access Octave's
documented internal variables and built-in symbolic constants.

</P>
<P>
Case is significant in variable names.  The symbols <CODE>a</CODE> and
<CODE>A</CODE> are distinct variables.

</P>
<P>
A variable name is a valid expression by itself.  It represents the
variable's current value.  Variables are given new values with
<STRONG>assignment operators</STRONG> and <STRONG>increment operators</STRONG>.
See section <A HREF="octave_9.html#SEC74">Assignment Expressions</A>.

</P>
<P>
A number of variables have special built-in meanings.  For example,
<CODE>ans</CODE> holds the most recently computed result, and <CODE>pi</CODE> names the
ratio of the circumference of a circle to its diameter. See section <A HREF="octave_8.html#SEC62">Summary of Built-in Variables</A>, for a list of all the predefined variables.  Some
of these built-in symbols are constants and may not be changed.  Others
can be used and assigned just like all other variables, but their values
are also used or changed automatically by Octave.

</P>
<P>
Variables in Octave do not have fixed types, so it is possible to first
store a numeric value in a variable and then to later use the same name
to hold a string value in the same program.  Variables may not be used
before they have been given a value.  Doing so results in an error.

</P>



<H2><A NAME="SEC60" HREF="octave_toc.html#TOC60">Global Variables</A></H2>
<P>
<A NAME="IDX218"></A>
<A NAME="IDX219"></A>
<A NAME="IDX220"></A>

</P>
<P>
A variable that has been declared <STRONG>global</STRONG> may be accessed from
within a function body without having to pass it as a formal parameter.

</P>
<P>
A variable may be declared global using a <CODE>global</CODE> declaration
statement.  The following statements are all global declarations.

</P>

<PRE>
global a
global b = 2
global c = 3, d, e = 5
</PRE>

<P>
It is necessary declare a variable as global within a function body in
order to access it.  For example,

</P>

<PRE>
global x
function f ()
  x = 1;
endfunction
f ()
</PRE>

<P>
does <EM>not</EM> set the value of the global variable <CODE>x</CODE> to 1.  In
order to change the value of the global variable <CODE>x</CODE>, you must also
declare it to be global within the function body, like this

</P>

<PRE>
function f ()
  global x;
  x = 1;
endfunction
</PRE>

<P>
Passing a global variable in a function parameter list will
make a local copy and not modify the global value.  For example, given
the function

</P>

<PRE>
function f (x)
  x = 0
endfunction
</PRE>

<P>
and the definition of <CODE>x</CODE> as a global variable at the top level,

</P>

<PRE>
global x = 13
</PRE>

<P>
the expression

</P>

<PRE>
f (x)
</PRE>

<P>
will display the value of <CODE>x</CODE> from inside the function as 0,
but the value of <CODE>x</CODE> at the top level remains unchanged, because
the function works with a <EM>copy</EM> of its argument.

</P>
<P>
<DL>
<DT><U>Built-in Variable:</U> <B>warn_comma_in_global_decl</B>
<DD><A NAME="IDX221"></A>
If the value of <CODE>warn_comma_in_global_decl</CODE> is nonzero, a
warning is issued for statements like

</P>

<PRE>
global a = 1, b
</PRE>

<P>
which makes the variables <CODE>a</CODE> and <CODE>b</CODE> global and assigns the
value 1 to the variable <CODE>a</CODE>, because in this context, the comma is
not interpreted as a statement separator.

</P>
<P>
The default value of <CODE>warn_comma_in_global_decl</CODE> is nonzero.
</DL>

</P>
<P>
<DL>
<DT><U>initialize_global_variables:</U> <B></B>
<DD><A NAME="IDX222"></A>
if the value of <CODE>initialize_global_variables</CODE> is nonzero, global
variables are initialized to the value of the built-in variable
<CODE>default_global_variable_value</CODE>.

</P>
<P>
the default value of <CODE>initialize_global_variables</CODE> is zero.
</DL>

</P>
<P>
<DL>
<DT><U>default_global_variable_value:</U> <B></B>
<DD><A NAME="IDX223"></A>
if <CODE>initialize_global_variables</CODE> is nonzero, the value of
<CODE>default_glbaol_variable_value</CODE> is used as the initial value of
global variables that are not explicitly initialized.  for example,

</P>

<PRE>
initialize_global_variables = 1;
default_global_variable_value = 13;
global foo;
foo
     => 13
</PRE>

<P>
the variable <CODE>default_global_variable_value</CODE> is initially undefined.
</DL>

</P>
<P>
<DL>
<DT><U>Built-in Function:</U>  <B>is_global</B> <I>(<VAR>name</VAR>)</I>
<DD><A NAME="IDX224"></A>
Return 1 if <VAR>name</VAR> is globally visible.  Otherwise, return 0.  For
example,

</P>

<PRE>
global x
is_global ("x")
     => 1
</PRE>

</DL>



<H2><A NAME="SEC61" HREF="octave_toc.html#TOC61">Status of Variables</A></H2>

<P>
<DL>
<DT><U>Command:</U> <B>clear</B> <I>options pattern ...</I>
<DD><A NAME="IDX225"></A>
Delete the names matching the given patterns from the symbol table.  The
pattern may contain the following special characters:
<DL COMPACT>

<DT><CODE>?</CODE>
<DD>
Match any single character.

<DT><CODE>*</CODE>
<DD>
Match zero or more characters.

<DT><CODE>[ <VAR>list</VAR> ]</CODE>
<DD>
Match the list of characters specified by <VAR>list</VAR>.  If the first
character is <CODE>!</CODE> or <CODE>^</CODE>, match all characters except those
specified by <VAR>list</VAR>.  For example, the pattern <SAMP>`[a-zA-Z]'</SAMP> will
match all lower and upper case alphabetic characters. 
</DL>

<P>
For example, the command

</P>

<PRE>
clear foo b*r
</PRE>

<P>
clears the name <CODE>foo</CODE> and all names that begin with the letter
<CODE>b</CODE> and end with the letter <CODE>r</CODE>.

</P>
<P>
If <CODE>clear</CODE> is called without any arguments, all user-defined
variables (local and global) are cleared from the symbol table.  If
<CODE>clear</CODE> is called with at least one argument, only the visible
names matching the arguments are cleared.  For example, suppose you have
defined a function <CODE>foo</CODE>, and then hidden it by performing the
assignment <CODE>foo = 2</CODE>.  Executing the command <KBD>clear foo</KBD> once
will clear the variable definition and restore the definition of
<CODE>foo</CODE> as a function.  Executing <KBD>clear foo</KBD> a second time will
clear the function definition.

</P>
<P>
This command may not be used within a function body.
</DL>

</P>
<P>
<DL>
<DT><U>Command:</U> <B>who</B> <I>options pattern ...</I>
<DD><A NAME="IDX226"></A>
<DT><U>Command:</U> <B>whos</B> <I>options pattern ...</I>
<DD><A NAME="IDX227"></A>
List currently defined symbols matching the given patterns.  The
following are valid options.  They may be shortened to one character but
may not be combined.

</P>
<DL COMPACT>

<DT><CODE>-all</CODE>
<DD>
List all currently defined symbols.

<DT><CODE>-builtins</CODE>
<DD>
List built-in variables and functions.  This includes all currently
compiled function files, but does not include all function files that
are in the <CODE>LOADPATH</CODE>.

<DT><CODE>-functions</CODE>
<DD>
List user-defined functions.

<DT><CODE>-long</CODE>
<DD>
Print a long listing including the type and dimensions of any symbols.
The symbols in the first column of output indicate whether it is
possible to redefine the symbol, and whether it is possible for it to be
cleared.

<DT><CODE>-variables</CODE>
<DD>
List user-defined variables.
</DL>

<P>
Valid patterns are the same as described for the <CODE>clear</CODE> command
above.  If no patterns are supplied, all symbols from the given category
are listed.  By default, only user defined functions and variables
visible in the local scope are displayed.

</P>
<P>
The command <KBD>whos</KBD> is equivalent to <KBD>who -long</KBD>.
</DL>

</P>
<P>
<DL>
<DT><U>Built-in Function:</U>  <B>exist</B> <I>(<VAR>name</VAR>)</I>
<DD><A NAME="IDX228"></A>
Return 1 if the name exists as a variable, 2 if the name (after
appending <SAMP>`.m'</SAMP>) is a function file in the path, 3 if the name is a
<SAMP>`.oct'</SAMP> file in the path, or 5 if the name is a built-in function.
Otherwise, return 0.
</DL>

</P>
<P>
<DL>
<DT><U>Built-in Function:</U>  <B>document</B> <I>(<VAR>symbol</VAR>, <VAR>text</VAR>)</I>
<DD><A NAME="IDX229"></A>
Set the documentation string for <VAR>symbol</VAR> to <VAR>text</VAR>.
</DL>

</P>
<P>
<DL>
<DT><U>Command:</U> <B>type</B> <I>options name ...</I>
<DD><A NAME="IDX230"></A>
Display the definition of each <VAR>name</VAR> that refers to a function.

</P>
<P>
Normally also displays if each <VAR>name</VAR> is user-defined or builtin;
the <CODE>-q</CODE> option suppresses this behaviour.

</P>
<P>
Currently, Octave can only display functions that can be compiled
cleanly, because it uses its internal representation of the function to
recreate the program text.

</P>
<P>
Comments are not displayed because Octave's parser currently discards
them as it converts the text of a function file to its internal
representation.  This problem may be fixed in a future release.
</DL>

</P>
<P>
<DL>
<DT><U>Command:</U> <B>which</B> <I>name ...</I>
<DD><A NAME="IDX231"></A>
Display the type of each <VAR>name</VAR>.  If <VAR>name</VAR> is defined from a
function file, the full name of the file is also displayed.
</DL>

</P>


<H2><A NAME="SEC62" HREF="octave_toc.html#TOC62">Summary of Built-in Variables</A></H2>

<P>
Here is a summary of all of Octave's built-in variables along with
cross references to additional information and their default values.  In
the following table <VAR>octave-home</VAR> stands for the root directory
where all of Octave is installed (the default is <TT>`/usr/local'</TT>,
<VAR>version</VAR> stands for the Octave version number (for example,
2.0.13) and <VAR>arch</VAR> stands for the type of system for which
Octave was compiled (for example, <CODE>i586-pc-linux-gnu</CODE>).

</P>
<DL COMPACT>

<DT><CODE>DEFAULT_LOADPATH</CODE>
<DD>
<A NAME="IDX232"></A>
See section <A HREF="octave_12.html#SEC95">Function Files</A>.

Default value: <CODE>".:<VAR>octave-home</VAR>/lib/<VAR>version</VAR>"</CODE>.

<DT><CODE>EDITOR</CODE>
<DD>
<A NAME="IDX233"></A>
See section <A HREF="octave_3.html#SEC35">Commands For Manipulating The History</A>.

Default value: <CODE>"emacs"</CODE>.

<DT><CODE>EXEC_PATH</CODE>
<DD>
<A NAME="IDX234"></A>
See section <A HREF="octave_30.html#SEC168">Controlling Subprocesses</A>.

Default value: <CODE>":$PATH"</CODE>.

<DT><CODE>INFO_FILE</CODE>
<DD>
<A NAME="IDX235"></A>
See section <A HREF="octave_3.html#SEC29">Commands for Getting Help</A>.

Default value: <CODE>"<VAR>octave-home</VAR>/info/octave.info"</CODE>.

<DT><CODE>INFO_PROGRAM</CODE>
<DD>
<A NAME="IDX236"></A>
See section <A HREF="octave_3.html#SEC29">Commands for Getting Help</A>.

Default value: <CODE>"<VAR>octave-home</VAR>/libexec/octave/<VAR>version</VAR>/exec/<VAR>arch</VAR>/info"</CODE>.

<DT><CODE>LOADPATH</CODE>
<DD>
<A NAME="IDX237"></A>
See section <A HREF="octave_12.html#SEC95">Function Files</A>.

Default value: <CODE>":"</CODE>, which tells Octave to use the directories
specified by the built-in variable <CODE>DEFAULT_LOADPATH</CODE>.

<DT><CODE>OCTAVE_HOME</CODE>
<DD>
<A NAME="IDX238"></A>

Default value: <CODE>"/usr/local"</CODE>.

<DT><CODE>PAGER</CODE>
<DD>
<A NAME="IDX239"></A>
See section <A HREF="octave_14.html#SEC100">Input and Output</A>.

Default value: <CODE>"less", or "more"</CODE>.

<DT><CODE>PS1</CODE>
<DD>
<A NAME="IDX240"></A>
See section <A HREF="octave_3.html#SEC36">Customizing the Prompt</A>.

Default value: <CODE>"\s:\#&#62; "</CODE>.

<DT><CODE>PS2</CODE>
<DD>
<A NAME="IDX241"></A>
See section <A HREF="octave_3.html#SEC36">Customizing the Prompt</A>.

Default value: <CODE>"&#62; "</CODE>.

<DT><CODE>PS4</CODE>
<DD>
<A NAME="IDX242"></A>
See section <A HREF="octave_3.html#SEC36">Customizing the Prompt</A>.

Default value: <CODE>"+ "</CODE>.

<DT><CODE>auto_unload_dot_oct_files</CODE>
<DD>
<A NAME="IDX243"></A>
See section <A HREF="octave_12.html#SEC97">Dynamically Linked Functions</A>.

Default value: 0.

<DT><CODE>automatic_replot</CODE>
<DD>
<A NAME="IDX244"></A>
See section <A HREF="octave_15.html#SEC126">Two-Dimensional Plotting</A>.

Default value: 0.

<DT><CODE>beep_on_error</CODE>
<DD>
<A NAME="IDX245"></A>
See section <A HREF="octave_13.html#SEC99">Error Handling</A>.

Default value: 0.

<DT><CODE>completion_append_char</CODE>
<DD>
<A NAME="IDX246"></A>
See section <A HREF="octave_3.html#SEC34">Letting Readline Type For You</A>.

Default value: <CODE>" "</CODE>.

<DT><CODE>default_eval_print_flag</CODE>
<DD>
<A NAME="IDX247"></A>
See section <A HREF="octave_10.html#SEC77">Evaluation</A>.

Default value: 1.

<DT><CODE>default_return_value</CODE>
<DD>
<A NAME="IDX248"></A>
See section <A HREF="octave_12.html#SEC91">Multiple Return Values</A>.

Default value: <CODE>[]</CODE>.

<DT><CODE>default_save_format</CODE>
<DD>
<A NAME="IDX249"></A>
See section <A HREF="octave_14.html#SEC104">Simple File I/O</A>.

Default value: <CODE>"ascii"</CODE>.

<DT><CODE>do_fortran_indexing</CODE>
<DD>
<A NAME="IDX250"></A>
See section <A HREF="octave_9.html#SEC65">Index Expressions</A>.

Default value: 0.

<DT><CODE>crash_dumps_octave_core</CODE>
<DD>
<A NAME="IDX251"></A>
See section <A HREF="octave_14.html#SEC104">Simple File I/O</A>.

Default value: 1.

<DT><CODE>define_all_return_values</CODE>
<DD>
<A NAME="IDX252"></A>
See section <A HREF="octave_12.html#SEC91">Multiple Return Values</A>.

Default value: 0.

<DT><CODE>empty_list_elements_ok</CODE>
<DD>
<A NAME="IDX253"></A>
See section <A HREF="octave_5.html#SEC50">Empty Matrices</A>.

Default value: <CODE>"warn"</CODE>.

<DT><CODE>fixed_point_format</CODE>
<DD>
<A NAME="IDX254"></A>
See section <A HREF="octave_5.html#SEC49">Matrices</A>

Default value: 0.

<DT><CODE>gnuplot_binary</CODE>
<DD>
<A NAME="IDX255"></A>
See section <A HREF="octave_15.html#SEC128">Three-Dimensional Plotting</A>.

Default value: <CODE>"gnuplot"</CODE>.

<DT><CODE>history_file</CODE>
<DD>
<A NAME="IDX256"></A>
See section <A HREF="octave_3.html#SEC35">Commands For Manipulating The History</A>.

Default value: <CODE>"~/.octave_hist"</CODE>.

<DT><CODE>history_size</CODE>
<DD>
<A NAME="IDX257"></A>
See section <A HREF="octave_3.html#SEC35">Commands For Manipulating The History</A>.

Default value: 1024.

<DT><CODE>ignore_function_time_stamp</CODE>
<DD>
<A NAME="IDX258"></A>
See section <A HREF="octave_12.html#SEC95">Function Files</A>.

Default value: <CODE>"system"</CODE>.

<DT><CODE>implicit_num_to_str_ok</CODE>
<DD>
<A NAME="IDX259"></A>
See section <A HREF="octave_6.html#SEC56">String Conversions</A>.

Default value: 0.

<DT><CODE>implicit_str_to_num_ok</CODE>
<DD>
<A NAME="IDX260"></A>
See section <A HREF="octave_6.html#SEC56">String Conversions</A>.

Default value: 0.

<DT><CODE>max_recursion_depth</CODE>
<DD>
<A NAME="IDX261"></A>
See section <A HREF="octave_9.html#SEC68">Recursion</A>.

Default value: 256.

<DT><CODE>ok_to_lose_imaginary_part</CODE>
<DD>
<A NAME="IDX262"></A>
See section <A HREF="octave_16.html#SEC134">Special Utility Matrices</A>.

Default value: <CODE>"warn"</CODE>.

<DT><CODE>output_max_field_width</CODE>
<DD>
<A NAME="IDX263"></A>
See section <A HREF="octave_5.html#SEC49">Matrices</A>.

Default value: 10.

<DT><CODE>output_precision</CODE>
<DD>
<A NAME="IDX264"></A>
See section <A HREF="octave_5.html#SEC49">Matrices</A>.

Default value: 5.

<DT><CODE>page_screen_output</CODE>
<DD>
<A NAME="IDX265"></A>
See section <A HREF="octave_14.html#SEC100">Input and Output</A>.

Default value: 1.

<DT><CODE>prefer_column_vectors</CODE>
<DD>
<A NAME="IDX266"></A>
See section <A HREF="octave_9.html#SEC65">Index Expressions</A>.

Default value: 1.

<DT><CODE>print_answer_id_name</CODE>
<DD>
<A NAME="IDX267"></A>
See section <A HREF="octave_14.html#SEC102">Terminal Output</A>.

Default value: 1.

<DT><CODE>print_empty_dimensions</CODE>
<DD>
<A NAME="IDX268"></A>
See section <A HREF="octave_5.html#SEC50">Empty Matrices</A>.

Default value: 1.

<DT><CODE>resize_on_range_error</CODE>
<DD>
<A NAME="IDX269"></A>
See section <A HREF="octave_9.html#SEC65">Index Expressions</A>.

Default value: 1.

<DT><CODE>return_last_computed_value</CODE>
<DD>
<A NAME="IDX270"></A>
See section <A HREF="octave_12.html#SEC94">Returning From a Function</A>.

Default value: 0.

<DT><CODE>save_precision</CODE>
<DD>
<A NAME="IDX271"></A>
See section <A HREF="octave_14.html#SEC104">Simple File I/O</A>.

Default value: 17.

<DT><CODE>saving_history</CODE>
<DD>
<A NAME="IDX272"></A>
See section <A HREF="octave_3.html#SEC35">Commands For Manipulating The History</A>.

Default value: 1.

<DT><CODE>silent_functions</CODE>
<DD>
<A NAME="IDX273"></A>
See section <A HREF="octave_12.html#SEC90">Defining Functions</A>.

Default value: 0.

<DT><CODE>split_long_rows</CODE>
<DD>
<A NAME="IDX274"></A>
See section <A HREF="octave_5.html#SEC49">Matrices</A>.

Default value: 1.

<DT><CODE>struct_levels_to_print</CODE>
<DD>
<A NAME="IDX275"></A>
See section <A HREF="octave_7.html#SEC58">Data Structures</A>.

Default value: 2.

<DT><CODE>suppress_verbose_help_message</CODE>
<DD>
<A NAME="IDX276"></A>
See section <A HREF="octave_3.html#SEC29">Commands for Getting Help</A>.

Default value: 1.

<DT><CODE>treat_neg_dim_as_zero</CODE>
<DD>
<A NAME="IDX277"></A>
See section <A HREF="octave_16.html#SEC134">Special Utility Matrices</A>.

Default value: 0.

<DT><CODE>warn_assign_as_truth_value</CODE>
<DD>
<A NAME="IDX278"></A>
See section <A HREF="octave_11.html#SEC79">The <CODE>if</CODE> Statement</A>.

Default value: 1.

<DT><CODE>warn_comma_in_global_decl</CODE>
<DD>
<A NAME="IDX279"></A>
See section <A HREF="octave_8.html#SEC60">Global Variables</A>.

Default value: 1.

<DT><CODE>warn_divide_by_zero</CODE>
<DD>
<A NAME="IDX280"></A>
See section <A HREF="octave_9.html#SEC69">Arithmetic Operators</A>.

Default value: 1.

<DT><CODE>warn_function_name_clash</CODE>
<DD>
<A NAME="IDX281"></A>
See section <A HREF="octave_12.html#SEC95">Function Files</A>.

Default value: 1.

<DT><CODE>warn_reload_forces_clear</CODE>
<DD>
<A NAME="IDX282"></A>
See section <A HREF="octave_12.html#SEC97">Dynamically Linked Functions</A>.

Default value: 1.

<DT><CODE>warn_variable_switch_label</CODE>
<DD>
<A NAME="IDX283"></A>
See section <A HREF="octave_11.html#SEC80">The <CODE>switch</CODE> Statement</A>.

Default value: 0.

<DT><CODE>whitespace_in_literal_matrix</CODE>
<DD>
<A NAME="IDX284"></A>
See section <A HREF="octave_5.html#SEC49">Matrices</A>.

Default value: <CODE>""</CODE>.
</DL>



<H2><A NAME="SEC63" HREF="octave_toc.html#TOC63">Defaults from the Environment</A></H2>

<P>
Octave uses the values of the following environment variables to set the
default values for the corresponding built-in variables.  In addition,
the values from the environment may be overridden by command-line
arguments.  See section <A HREF="octave_3.html#SEC26">Command Line Options</A>.

</P>
<DL COMPACT>

<DT><CODE>EDITOR</CODE>
<DD>
<A NAME="IDX285"></A>
See section <A HREF="octave_3.html#SEC35">Commands For Manipulating The History</A>.

Built-in variable: <CODE>EDITOR</CODE>.

<DT><CODE>OCTAVE_EXEC_PATH</CODE>
<DD>
<A NAME="IDX286"></A>
See section <A HREF="octave_30.html#SEC168">Controlling Subprocesses</A>.

Built-in variable: <CODE>EXEC_PATH</CODE>.
Command-line argument: <CODE>--exec-path</CODE>.

<DT><CODE>OCTAVE_PATH</CODE>
<DD>
<A NAME="IDX287"></A>
See section <A HREF="octave_12.html#SEC95">Function Files</A>.

Built-in variable: <CODE>LOADPATH</CODE>.
Command-line argument: <CODE>--path</CODE>.

<DT><CODE>OCTAVE_INFO_FILE</CODE>
<DD>
<A NAME="IDX288"></A>
See section <A HREF="octave_3.html#SEC29">Commands for Getting Help</A>.

Built-in variable: <CODE>INFO_FILE</CODE>.
Command-line argument: <CODE>--info-file</CODE>.

<DT><CODE>OCTAVE_INFO_PROGRAM</CODE>
<DD>
<A NAME="IDX289"></A>
See section <A HREF="octave_3.html#SEC29">Commands for Getting Help</A>.

Built-in variable: <CODE>INFO_PROGRAM</CODE>.
Command-line argument: <CODE>--info-program</CODE>.

<DT><CODE>OCTAVE_HISTSIZE</CODE>
<DD>
<A NAME="IDX290"></A>
See section <A HREF="octave_3.html#SEC35">Commands For Manipulating The History</A>.

Built-in variable: <CODE>history_size</CODE>.

<DT><CODE>OCTAVE_HISTFILE</CODE>
<DD>
<A NAME="IDX291"></A>
See section <A HREF="octave_3.html#SEC35">Commands For Manipulating The History</A>.

Built-in variable: <CODE>history_file</CODE>.
</DL>

<P><HR><P>
Go to the <A HREF="octave_1.html">first</A>, <A HREF="octave_7.html">previous</A>, <A HREF="octave_9.html">next</A>, <A HREF="octave_40.html">last</A> section, <A HREF="octave_toc.html">table of contents</A>.
</BODY>
</HTML>