Updated with messages about gh_write and scm_internal_stack_catch.
authorMikael Djurfeldt <djurfeldt@nada.kth.se>
Mon, 25 Aug 1997 13:33:13 +0000 (13:33 +0000)
committerMikael Djurfeldt <djurfeldt@nada.kth.se>
Mon, 25 Aug 1997 13:33:13 +0000 (13:33 +0000)
NEWS

diff --git a/NEWS b/NEWS
index 4492ed3..77284ef 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -206,8 +206,26 @@ value for NAME.
 
 * Changes to the gh_ interface
 
+** Function: void gh_write (SCM x)
+
+Write the printed representation of the scheme object x to the current
+output port.  Corresponds to the scheme level `write'.
+
 * Changes to the scm_ interface
 
+** Function: SCM scm_internal_stack_catch (SCM tag,
+                                          scm_catch_body_t body,
+                                          void *body_data,
+                                          scm_catch_handler_t handler,
+                                          void *handler_data)
+
+A new sibling to the other two C level `catch' functions
+scm_internal_catch and scm_internal_lazy_catch.  Use it if you want
+the stack to be saved automatically into the variable `the-last-stack'
+(scm_the_last_stack_var) on error.  This is necessary if you want to
+use advanced error reporting, such as calling scm_display_error and
+scm_display_backtrace.  (They both take a stack object as argument.)
+
 ** The hook scm_error_callback has been removed.  It was originally
 intended as a way for the user to install his own error handler.  But
 that method works badly since it intervenes between throw and catch,