[Emacs-diffs] Changes to emacs/lispref/compile.texi [lexbind]

[Miles Bader]

Index: emacs/lispref/compile.texi
diff -c emacs/lispref/compile.texi:1.12.8.4 emacs/lispref/compile.texi:1.12.8.5
*** emacs/lispref/compile.texi:1.12.8.4 Tue Feb 17 23:15:45 2004
--- emacs/lispref/compile.texi  Tue Jul  6 09:23:49 2004
***************
*** 171,176 ****
--- 171,180 ----
  operand of an instruction.  The vector contains all the constants,
  variable names and function names used by the function, except for
  certain primitives that are coded as special instructions.
+ 
+ If the argument to @code{byte-compile} is a @code{lambda} expression,
+ it returns the corresponding compiled code, but does not store
+ it anywhere.
  @end defun
  
  @deffn Command compile-defun &optional arg
***************
*** 232,238 ****
  When a @samp{.el} file has no corresponding @samp{.elc} file,
  @var{flag} says what to do.  If it is @code{nil}, this command ignores
  these files.  If @var{flag} is 0, it compiles them.  If it is neither
! @code{nil} nor 0, it asks the user whether to compile each such file.
  
  Interactively, @code{byte-recompile-directory} prompts for
  @var{directory} and @var{flag} is the prefix argument.
--- 236,243 ----
  When a @samp{.el} file has no corresponding @samp{.elc} file,
  @var{flag} says what to do.  If it is @code{nil}, this command ignores
  these files.  If @var{flag} is 0, it compiles them.  If it is neither
! @code{nil} nor 0, it asks the user whether to compile each such file,
! and asks about each subdirectory as well.
  
  Interactively, @code{byte-recompile-directory} prompts for
  @var{directory} and @var{flag} is the prefix argument.
***************
*** 293,300 ****
  
  @item
  If you alter the compiled file (such as by compiling a new version),
! then further access to documentation strings in this file will give
! nonsense results.
  @end itemize
  
    If your site installs Emacs following the usual procedures, these
--- 298,305 ----
  
  @item
  If you alter the compiled file (such as by compiling a new version),
! then further access to documentation strings in this file will
! probably give nonsense results.
  @end itemize
  
    If your site installs Emacs following the usual procedures, these
***************
*** 365,372 ****
  
  @item
  If you alter the compiled file (such as by compiling a new version),
! then trying to load any function not already loaded will yield nonsense
! results.
  @end itemize
  
    These problems will never happen in normal circumstances with
--- 370,377 ----
  
  @item
  If you alter the compiled file (such as by compiling a new version),
! then trying to load any function not already loaded will usually yield
! nonsense results.
  @end itemize
  
    These problems will never happen in normal circumstances with
***************
*** 391,399 ****
  @end defvar
  
  @defun fetch-bytecode function
! This immediately finishes loading the definition of @var{function} from
! its byte-compiled file, if it is not fully loaded already.  The argument
! @var{function} may be a byte-code function object or a function name.
  @end defun
  
  @node Eval During Compile
--- 396,405 ----
  @end defvar
  
  @defun fetch-bytecode function
! If @var{function} is a byte-code function object, this immediately
! finishes loading the byte code of @var{function} from its
! byte-compiled file, if it is not fully loaded already.  Otherwise,
! it does nothing.  It always returns @var{function}.
  @end defun
  
  @node Eval During Compile
***************
*** 440,446 ****
  you must search for the function names.
  
    You can suppress the compiler warning for calling an undefined
! function @var{func} by conditionalizing the function call on a
  @code{fboundp} test, like this:
  
  @example
--- 446,452 ----
  you must search for the function names.
  
    You can suppress the compiler warning for calling an undefined
! function @var{func} by conditionalizing the function call on an
  @code{fboundp} test, like this:
  
  @example
***************
*** 468,481 ****
    You can suppress any compiler warnings using the construct
  @code{with-no-warnings}:
  
! @defmac with-no-warnings body...
  In execution, this is equivalent to @code{(progn @var{body}...)},
  but the compiler does not issue warnings for anything that occurs
  inside @var{body}.
  
  We recommend that you use this construct around the smallest
  possible piece of code.
! @end defmac
  
  @node Byte-Code Objects
  @section Byte-Code Function Objects
--- 474,490 ----
    You can suppress any compiler warnings using the construct
  @code{with-no-warnings}:
  
! @c This is implemented with a defun, but conceptually it is
! @c a special form.
! 
! @defspec with-no-warnings body...
  In execution, this is equivalent to @code{(progn @var{body}...)},
  but the compiler does not issue warnings for anything that occurs
  inside @var{body}.
  
  We recommend that you use this construct around the smallest
  possible piece of code.
! @end defspec
  
  @node Byte-Code Objects
  @section Byte-Code Function Objects
***************
*** 578,584 ****
  point is left before the output.
  
  The argument @var{object} can be a function name, a lambda expression
! or a byte-code object.
  @end deffn
  
    Here are two examples of using the @code{disassemble} function.  We
--- 587,594 ----
  point is left before the output.
  
  The argument @var{object} can be a function name, a lambda expression
! or a byte-code object.  If it is a lambda expression, @code{disassemble}
! compiles it and disassembles the resulting compiled code.
  @end deffn
  
    Here are two examples of using the @code{disassemble} function.  We