From 39f624fabd6ffe3f79aa6b66588b48af368494be Mon Sep 17 00:00:00 2001 From: =?utf8?q?Pavel=20Jan=C3=ADk?= Date: Sat, 20 Oct 2001 15:11:10 +0000 Subject: [PATCH] Change doc-string comments to `new style' [w/`doc:' keyword]. --- src/ChangeLog | 5 +++++ src/bytecode.c | 32 ++++++++++++++++---------------- 2 files changed, 21 insertions(+), 16 deletions(-) diff --git a/src/ChangeLog b/src/ChangeLog index 0e7071be054..175ae0adbe5 100644 --- a/src/ChangeLog +++ b/src/ChangeLog @@ -1,3 +1,8 @@ +2001-10-20 Pavel Jan,Bm(Bk + + * bytecode.c: Change doc-string comments to `new style' [w/`doc:' + keyword]. + 2001-10-20 Miles Bader The following changes remove the glyph_row `inverse_p' field, diff --git a/src/bytecode.c b/src/bytecode.c index f8ecc4f64c0..c356eb3a262 100644 --- a/src/bytecode.c +++ b/src/bytecode.c @@ -412,12 +412,12 @@ unmark_byte_stack () DEFUN ("byte-code", Fbyte_code, Sbyte_code, 3, 3, 0, - "Function used internally in byte-compiled code.\n\ -The first argument, BYTESTR, is a string of byte code;\n\ -the second, VECTOR, a vector of constants;\n\ -the third, MAXDEPTH, the maximum stack depth used in this function.\n\ -If the third argument is incorrect, Emacs may crash.") - (bytestr, vector, maxdepth) + doc: /* Function used internally in byte-compiled code. +The first argument, BYTESTR, is a string of byte code; +the second, VECTOR, a vector of constants; +the third, MAXDEPTH, the maximum stack depth used in this function. +If the third argument is incorrect, Emacs may crash. */) + (bytestr, vector, maxdepth) Lisp_Object bytestr, vector, maxdepth; { int count = specpdl_ptr - specpdl; @@ -1746,18 +1746,18 @@ syms_of_bytecode () #ifdef BYTE_CODE_METER DEFVAR_LISP ("byte-code-meter", &Vbyte_code_meter, - "A vector of vectors which holds a histogram of byte-code usage.\n\ -\(aref (aref byte-code-meter 0) CODE) indicates how many times the byte\n\ -opcode CODE has been executed.\n\ -\(aref (aref byte-code-meter CODE1) CODE2), where CODE1 is not 0,\n\ -indicates how many times the byte opcodes CODE1 and CODE2 have been\n\ -executed in succession."); + doc: /* A vector of vectors which holds a histogram of byte-code usage. +\(aref (aref byte-code-meter 0) CODE) indicates how many times the byte +opcode CODE has been executed. +\(aref (aref byte-code-meter CODE1) CODE2), where CODE1 is not 0, +indicates how many times the byte opcodes CODE1 and CODE2 have been +executed in succession. */); DEFVAR_BOOL ("byte-metering-on", &byte_metering_on, - "If non-nil, keep profiling information on byte code usage.\n\ -The variable byte-code-meter indicates how often each byte opcode is used.\n\ -If a symbol has a property named `byte-code-meter' whose value is an\n\ -integer, it is incremented each time that symbol's function is called."); + doc: /* If non-nil, keep profiling information on byte code usage. +The variable byte-code-meter indicates how often each byte opcode is used. +If a symbol has a property named `byte-code-meter' whose value is an +integer, it is incremented each time that symbol's function is called. */); byte_metering_on = 0; Vbyte_code_meter = Fmake_vector (make_number (256), make_number (0)); -- 2.39.5