[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#23873: Advised fill-paragraph breaks kotl-mode

From: Robert Weiner
Subject: bug#23873: Advised fill-paragraph breaks kotl-mode
Date: Thu, 30 Jun 2016 10:04:11 -0400

Dear Stephen:

Thank you for the very clear issue report.  The issue is that Emacs
now has an argument descriptor bitstring that is sometimes used in
place of the argument list as the first element of the bytecode as
summarized below.  We will have to find out how to extract the
arguments given such a code as the documentation does not provide any
information on that.  -- Bob

   Internally, a byte-code function object is much like a vector; its
elements can be accessed using ‘aref’.  Its printed representation is
like that for a vector, with an additional ‘#’ before the opening ‘[’.
It must have at least four elements; there is no maximum number, but
only the first six elements have any normal use.  They are:

     The descriptor of the arguments.  This can either be a list of
     arguments, as described in *note Argument List::, or an integer
     encoding the required number of arguments.  In the latter case, the
     value of the descriptor specifies the minimum number of arguments
     in the bits zero to 6, and the maximum number of arguments in bits
     8 to 14.  If the argument list uses ‘&rest’, then bit 7 is set;
     otherwise it’s cleared.

     If ARGDESC is a list, the arguments will be dynamically bound
     before executing the byte code.  If ARGDESC is an integer, the
     arguments will be instead pushed onto the stack of the byte-code
     interpreter, before executing the code.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]