Mercurial > hg > xemacs-beta
view man/new-users-guide/help.texi @ 4921:17362f371cc2
add more byte-code assertions and better failure output
-------------------- ChangeLog entries follow: --------------------
src/ChangeLog addition:
2010-02-03 Ben Wing <ben@xemacs.org>
* alloc.c (Fmake_byte_code):
* bytecode.h:
* lisp.h:
* lread.c:
* lread.c (readevalloop):
* lread.c (Fread):
* lread.c (Fread_from_string):
* lread.c (read_list_conser):
* lread.c (read_list):
* lread.c (vars_of_lread):
* symbols.c:
* symbols.c (Fdefine_function):
Turn on the "compiled-function annotation hack". Implement it
properly by hooking into Fdefalias(). Note in the docstring to
`defalias' that we do this. Remove some old broken code and
change code that implemented the old kludgy way of hooking into
the Lisp reader into bracketed by `#ifdef
COMPILED_FUNCTION_ANNOTATION_HACK_OLD_WAY', which is not enabled.
Also enable byte-code metering when DEBUG_XEMACS -- this is a form
of profiling for computing histograms of which sequences of two
bytecodes are used most often.
* bytecode-ops.h:
* bytecode-ops.h (OPCODE):
New file. Extract out all the opcodes and declare them using
OPCODE(), a bit like frame slots and such. This way the file can
be included multiple times if necessary to iterate multiple times
over the byte opcodes.
* bytecode.c:
* bytecode.c (NUM_REMEMBERED_BYTE_OPS):
* bytecode.c (OPCODE):
* bytecode.c (assert_failed_with_remembered_ops):
* bytecode.c (READ_UINT_2):
* bytecode.c (READ_INT_1):
* bytecode.c (READ_INT_2):
* bytecode.c (PEEK_INT_1):
* bytecode.c (PEEK_INT_2):
* bytecode.c (JUMP_RELATIVE):
* bytecode.c (JUMP_NEXT):
* bytecode.c (PUSH):
* bytecode.c (POP_WITH_MULTIPLE_VALUES):
* bytecode.c (DISCARD):
* bytecode.c (UNUSED):
* bytecode.c (optimize_byte_code):
* bytecode.c (optimize_compiled_function):
* bytecode.c (Fbyte_code):
* bytecode.c (vars_of_bytecode):
* bytecode.c (init_opcode_table_multi_op):
* bytecode.c (reinit_vars_of_bytecode):
* emacs.c (main_1):
* eval.c (funcall_compiled_function):
* symsinit.h:
Any time we change either the instruction pointer or the stack
pointer, assert that we're going to move it to a valid location.
This should catch failures right when they occur rather than
sometime later. This requires that we pass in another couple of
parameters into some functions (only with error-checking enabled,
see below).
Also keep track, using a circular queue, of the last 100 byte
opcodes seen, and when we hit an assert failure during byte-code
execution, output the contents of the queue in a nice readable
fashion. This requires that bytecode-ops.h be included a second
time so that a table mapping opcodes to the name of their operation
can be constructed. This table is constructed in new function
reinit_vars_of_bytecode().
Everything in the last two paras happens only when
ERROR_CHECK_BYTE_CODE.
Add some longish comments describing how the arrays that hold the
stack and instructions, and the pointers used to access them, work.
* gc.c:
Import some code from my `latest-fix' workspace to mark the
staticpro's in order from lowest to highest, rather than highest to
lowest, so it's easier to debug when something goes wrong.
* lisp.h (abort_with_message): Renamed from abort_with_msg().
* symbols.c (defsymbol_massage_name_1):
* symbols.c (defsymbol_nodump):
* symbols.c (defsymbol):
* symbols.c (defkeyword):
* symeval.h (DEFVAR_SYMVAL_FWD_OBJECT):
Make the various calls to staticpro() instead call staticpro_1(),
passing in the name of the C var being staticpro'ed, so that it
shows up in staticpro_names. Otherwise staticpro_names just has
1000+ copies of the word `location'.
| author | Ben Wing <ben@xemacs.org> |
|---|---|
| date | Wed, 03 Feb 2010 08:01:55 -0600 |
| parents | 8de8e3f6228a |
| children |
line wrap: on
line source
@comment node-name, next, previous, up @node Help, Modes, Customization Basics, Top @chapter Help @cindex help XEmacs provides a comprehensive Help facility. On the extreme right of the menu-bar there is a @b{Help} menu. There are several help commands provided by this menu. You can also use @kbd{C-h} for invoking the Help facility. Type "?" for a list of keys you can type after typing @kbd{C-h}. If you want more information on what your options are and what kind of help you can get type "?" again. You will get a listing of all the keys you can type and what they will do. Initially if you want help, type @kbd{C-h} three times. @comment node-name, next, previous, up @menu * The Help Menu:: Items on the Help menu @end menu @node The Help Menu, , Help, Help @section Help menu @cindex help When you click on the Help menu with any of the mouse buttons you will get the following menu items: @table @b @item Info Selecting this item will take you to the Info page which is the online documentation browsing system. You can simply click on the highlighted items and "Info" will take you to the document providing information about that topic. @item Describe Mode After you select this item, you will get a documentation on the major and minor modes which are enabled in the buffer you are working with. @xref{Modes}, for information on Modes. @item Hyper Apropos... After you select this item, you will see the following message in the echo area: @example List symbols matching regexp: @end example @noindent If you type "mode" and hit @key{RET}, you will get a list of all the symbols (like functions and commands). You can now get documentation on any of the given symbols by "clicking" on any of the symbols (i.e. drag your mouse on the appropriate symbol and release the button). For example, if you "click" on the 'auto-fill-mode' you will get the following message in the window at the bottom: @example auto-fill-mode Function, Command: Toggle auto-fill mode. With arg, turn auto-fill mode on if and only if arg is positive. In auto-fill mode, inserting a space at a column beyond `fill-column' automatically breaks the line at a previous space. Variable: value = nil variable not documented @end example @item Command Apropos... Selecting this item will prompt you for a string just like when you select @b{Hyper Apropos...}. After you give a string name, you will get a listing of all the functions and commands containing that string name with a very short description about what that command does. @item Full Apropos... After you select this item, you will be prompted for a string name in the echo area: @example Apropos (regexp): @end example @noindent Now you can give any string name, for example "mode" and hit @key{RET}. You will get a listing of all the variables and commands containing that string i.e "mode" with a short description of its function. @item List Keybindings Select this item and you will get a listing of all the keys and the commands that they execute. Depending on which Major mode your buffer is in, you will get a listing of the special keybindings for that particular buffer also. For example, if you are in "Texinfo" mode, part of your list will contain: @example C-c C-c n texinfo-insert-@@node C-c C-c o texinfo-insert-@@noindent C-c C-c s texinfo-insert-@@samp C-c C-c t texinfo-insert-@@table C-c C-c v texinfo-insert-@@var C-c C-c x texinfo-insert-@@example C-c C-c @{ texinfo-insert-braces @end example @noindent These keybindings apply only to "Texinfo" mode. @xref{Modes}, for more information on various modes. @item Describe Key... After you select this item, you will be see the following message in the echo area: @example Describe Key: @end example After you type a command key sequence, full documentation of that command will be displayed. For example if you type @kbd{C-g}, you will see the following documentation for @kbd{C-g}: @kindex C-g @example keyboard-quit: Signal a `quit' condition. @end example This means that @kbd{C-g} will quit whatever command you gave earlier. @kindex C-h d @item Describe Function... This menu item provides documentation for a function. After you select this item, it will prompt you for a function name in the echo area: @example Describe function (default <some function name>): @end example @noindent If you hit @key{RET} without giving a function name, you will get documentation for that default function name, otherwise if you type a function name and hit @key{RET}, you will get documentation for the given function. @kindex C-h k @item Describe Variable... You can get documentation on any variable by selecting this menu item. It is similar to @b{Describe Function} and will prompt you for a variable name. @item Unix Manual... After you select this item you will be prompted for a Unix command for which you wish to see the man page. You will see the following message in the echo area: @example Manual entry: (default <some name>) @end example @noindent Now you can type any command, for example type @samp{who} and press @key{RET}. You will get the man page for the Unix command @samp{who} which lists who is on the system. @item Emacs Tutorial Select this item and you will get a tutorial on Emacs. It is good for new users. @item Emacs News Select this item and you will get a lot of historical and current news on Emacs ! @end table For more information on the Help facility, @xref{Help,,,xemacs,XEmacs User's Manual}.
