expose wrapped-exception introspect things for debugging
[8sync.git] / eightsync / agenda.scm
index 27c0d7d2371feb023853372035ad7e810391622f..9f54e17aa06ca2faf76c652de922e803bfb027af 100644 (file)
             
             catch-8sync catch-%8sync
 
             
             catch-8sync catch-%8sync
 
+            ;; used for introspecting the error, but a method for making
+            ;; is not exposed
+            wrapped-exception?
+            wrapped-exception-key wrapped-exception-args
+            wrapped-exception-stacks
+
             print-error-and-continue
 
             %current-agenda
             print-error-and-continue
 
             %current-agenda
@@ -512,7 +518,6 @@ return the wrong thing via (%8sync) and trip themselves up."
             ;; If something bad happened and we didn't catch it,
             ;; we'll wrap it up in such a way that the continuation
             ;; can address it
             ;; If something bad happened and we didn't catch it,
             ;; we'll wrap it up in such a way that the continuation
             ;; can address it
-            ;; @@: For this stack to work doesn't it have to be
             (lambda (key . args)
               (cond
                ((eq? key '8sync-caught-error)
             (lambda (key . args)
               (cond
                ((eq? key '8sync-caught-error)