comparison man/internals/internals.texi @ 173:8eaf7971accc r20-3b13

Import from CVS: tag r20-3b13
author cvs
date Mon, 13 Aug 2007 09:49:09 +0200
parents 538048ae2ab8
children 2d532a89d707
comparison
equal deleted inserted replaced
172:a38aed19690b 173:8eaf7971accc
1817 1817
1818 The names of the C arguments will be used as the names of the arguments 1818 The names of the C arguments will be used as the names of the arguments
1819 to the Lisp primitive as displayed in its documentation, modulo the same 1819 to the Lisp primitive as displayed in its documentation, modulo the same
1820 concerns described above for @code{F...} names (in particular, 1820 concerns described above for @code{F...} names (in particular,
1821 underscores in the C arguments become dashes in the Lisp arguments). 1821 underscores in the C arguments become dashes in the Lisp arguments).
1822 There is one additional kludge: A C argument called @code{defalt} 1822
1823 becomes the Lisp argument @code{default}. This deliberate misspelling 1823 There is one additional kludge: A trailing `_' on the C argument is
1824 is done because @code{default} is a reserved word in the C language. 1824 discarded when forming the Lisp argument. This allows C language
1825 reserved words (like @code{default}) or global symbols (like
1826 @code{dirname}) to be used as argument names without compiler warnings
1827 or errors.
1825 1828
1826 A Lisp function with @w{@var{max} = @code{UNEVALLED}} is a 1829 A Lisp function with @w{@var{max} = @code{UNEVALLED}} is a
1827 @w{@dfn{special form}}; its arguments are not evaluated. Instead it 1830 @w{@dfn{special form}}; its arguments are not evaluated. Instead it
1828 receives one argument of type @code{Lisp_Object}, a (Lisp) list of the 1831 receives one argument of type @code{Lisp_Object}, a (Lisp) list of the
1829 unevaluated arguments, conventionally named @code{(args)}. 1832 unevaluated arguments, conventionally named @code{(args)}.