Mercurial > octave-nkf

comparison doc/interpreter/external.txi @ 18075:24759ac2b8cb stable

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
doc: Periodic spellcheck of documentation * aspell-octave.en.pws: Remove WebKit from private dictionary. * external.txi: Fix typos and use two spaces for sentence breaks. * install.txi: Use @nospell macro around gl2ps. * rgb2ind.m: Correct British spelling of colour to American spelling.
author Rik <rik@octave.org>
date Wed, 04 Dec 2013 08:41:22 -0800
parents 3341d2f1e5db
children adb7c7e6a4a1
comparison
equal deleted inserted replaced
18073:42c3e30557a4 18075:24759ac2b8cb
1771 GCD of [10, 15] is 5 1771 GCD of [10, 15] is 5
1772 $ 1772 $
1773 @end group 1773 @end group
1774 @end example 1774 @end example
1775 1775
1776 It is worth noting that, if only builtin funcions are to be calle from 1776 It is worth noting that, if only builtin functions are to be called from
1777 a C++ standalone program, then it does not need to initialize the 1777 a C++ standalone program, then it does not need to initialize the
1778 interpreter to do so. The general rule is that, for a builtin 1778 interpreter to do so. The general rule is that, for a builtin
1779 function named @code{function_name} in the interpreter, there will be 1779 function named @code{function_name} in the interpreter, there will be
1780 a C++ function named @code{Ffunction_name} (note the prepended capital 1780 a C++ function named @code{Ffunction_name} (note the prepended capital
1781 @code{F}) accessible in the C++ API. The declarations for all builtin 1781 @code{F}) accessible in the C++ API@. The declarations for all builtin
1782 functions are collected in the header file @code{builtin-defun-decls.h}. 1782 functions are collected in the header file @code{builtin-defun-decls.h}.
1783 This feature should be used with care as the list of built-in functions can change. 1783 This feature should be used with care as the list of built-in functions can
1784 No guarantees can be made that a function that is currently built in won't be implemented 1784 change. No guarantees can be made that a function that is currently built in
1785 as a .m file or as a dynamically linked function in the future. 1785 won't be implemented as a .m file or as a dynamically linked function in the
1786 An example of how to call builtin functions from C++ can be seen in the code 1786 future. An example of how to call builtin functions from C++ can be seen in the
1787 code
1787 1788
1788 @example 1789 @example
1789 @EXAMPLEFILE(standalonebuiltin.cc) 1790 @EXAMPLEFILE(standalonebuiltin.cc)
1790 @end example 1791 @end example
1791 1792