[librep] Bumped the bytecode minor version. Document improvement. ChangeLog.
- From: Christopher Bratusek <chrisb src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [librep] Bumped the bytecode minor version. Document improvement. ChangeLog.
- Date: Sat, 3 Jul 2010 07:15:44 +0000 (UTC)
commit 4a3e91e2490f08a8c3b66056dbda2b6961070ab0
Author: Teika kazura <teika lavabit com>
Date: Sat Jun 26 15:16:31 2010 +0900
Bumped the bytecode minor version. Document improvement. ChangeLog.
ChangeLog | 4 +++-
lisp/rep/vm/bytecode-defs.jl | 3 ++-
man/lang.texi | 28 ++++++++++++++--------------
man/news.texi | 18 +++++++++---------
src/bytecodes.h | 4 +++-
5 files changed, 31 insertions(+), 26 deletions(-)
---
diff --git a/ChangeLog b/ChangeLog
index 77b6a0c..25e2f39 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,8 +1,10 @@
2010-06-26 Teika Kazura <teika lavabit com>
* lisp/rep/lang/interpreter.jl
- * lisp/rep/vm/compiler/rep.jl
+ * lisp/rep/vm/bytecode-defs.jl
+ * lisp/rep/vm/compiler/rep.jl
* man/lang.texi
* man/news.texi
+ * src/bytecodes.h
* src/lisp.c: Backtrace and debugger option fix.
Previously, if 'backtrace-on-error' is t, then it is printed even if
it's inside of a 'condition-case'. Now, it doesn't. Similar for
diff --git a/lisp/rep/vm/bytecode-defs.jl b/lisp/rep/vm/bytecode-defs.jl
index b8eda6c..9d30423 100644
--- a/lisp/rep/vm/bytecode-defs.jl
+++ b/lisp/rep/vm/bytecode-defs.jl
@@ -35,8 +35,9 @@
(open rep)
;; Instruction set version
+ ;; Don't forget to update the version number in src/bytecodes.h
(defconst bytecode-major 11)
- (defconst bytecode-minor 0)
+ (defconst bytecode-minor 1)
;; macro to get a named bytecode
(defmacro bytecode (name)
diff --git a/man/lang.texi b/man/lang.texi
index e44afc6..2bf2bca 100644
--- a/man/lang.texi
+++ b/man/lang.texi
@@ -5060,29 +5060,29 @@ is a string formatted by @var{template} and @var{VALUES}. (@pxref{Formatted Outp
@end defun
@defvar debug-on-error
-This variable is consulted by the function @code{signal}. If its value
-is either non-nil or a list containing the @var{error-symbol} to
- code{signal} as one of its elements, the Lisp debugger is entered.
+This variable controls the condition to enter the Lisp debugger.
When the debugger exits the error is signalled as normal.
-More exactly, if it's a symbol @code{always} or a list, then the
-debugger is entered always. If some other non-nil value, then it's
-ignored if an error is signalled from the inside of
- code{condition-case} described below. Notice that it's not checked if
-the error is actually handled by an error handler defined in
- code{condition-case}
+If it's @code{t}, then the debugger starts if the control is not
+inside of any @code{condition-case} described below. Notice that the
+criterion is NOT if the error is actually handled by an error handler.
+
+If it's a symbol @code{always}, then the debugger is entered always,
+i.e. even if it is inside of a @code{condition-case}. If it's a list
+of errer-symbols, for example @code{(void-value bad-arg)}, then only
+when the error matches one of them, the debugger is called even
+inside of a @code{condition-case}.
@lisp
(setq backtrace-on-error t) ;; Ordinary usage.
-(setq backtrace-on-error '(void-value bad-arg))
- ;; Enter debugger for only these two cases
+(setq backtrace-on-error '(void-value bad-arg)) ;; Catch them only
@end lisp
@end defvar
@defvar backtrace-on-error
-Similar to @code{debug-on-error}, but instead of entering the
-debugger, the current backtrace is printed to the standard error
-stream, and control continues.
+Similar to @code{debug-on-error} (read WELL its description), but
+instead of entering the debugger, the current backtrace is printed to
+the standard error stream, and control continues.
@end defvar
When you expect an error to occur and need to be able to regain control
diff --git a/man/news.texi b/man/news.texi
index 0499d70..e1bb6ca 100644
--- a/man/news.texi
+++ b/man/news.texi
@@ -8,21 +8,21 @@
@item Important notice
-You have to byte compile all codes again. Otherwise they may emit many
-messages. In particular @file{sawfish-config} is likely to crash. It
-is due to the backtrace change described below.
+You have to byte compile all codes again.
@item Half way improvement of @code{debug-on-error} and @code{backtrace-on-error} [Teika Kazura]
Previously, setting these values to @code{t} triggered the debugger /
the backtrace even if the error is signalled inside of
- code{condition-case} Now, they don't. Previous behavior can be
-obtained by setting them to a symbol @code{always}.
+ code{condition-case} This behavior can be still obtained by setting
+them to a symbol @code{always}.
-The default value of @code{backtrace-on-error} is @code{t}.
- emph{Please} notice that in this case, even if the error is not
-handled by an error handler, then the debugger / the backtrace is not
-invoked. It is not the best, but we can't improve it.
+Now, if they're @code{t}, the debugger / the backtrace is invoked only
+if the control is not inside of any @code{condition-case}. Notice that
+the condition is NOT if the error is actually handled by an error
+handler. It is not the best, but we can't improve it.
+
+The default value of @code{backtrace-on-error} is now @code{t}.
@item When you evaluate a closure, the module to which it belongs is printed, too. [Teika kazura]
diff --git a/src/bytecodes.h b/src/bytecodes.h
index bd8c2bc..c07c225 100644
--- a/src/bytecodes.h
+++ b/src/bytecodes.h
@@ -21,8 +21,10 @@
#ifndef BYTECODES_H
#define BYTECODES_H
+/* Don't forget to update the version number
+ * in lisp/rep/vm/bytecode-defs.jl, too. */
#define BYTECODE_MAJOR_VERSION 11
-#define BYTECODE_MINOR_VERSION 0
+#define BYTECODE_MINOR_VERSION 1
/* Number of bits encoded in each extra opcode forming the argument. */
#define ARG_SHIFT 8
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]