From 07541fdcdc2fd8f5eecbfead5094bf2c613ff515 Mon Sep 17 00:00:00 2001 From: David Lichteblau Date: Sun, 6 Apr 2008 19:09:38 +0200 Subject: [PATCH] Disabled cerror for now --- TEST | 2 +- xslt.lisp | 13 +++++++++++++ 2 files changed, 14 insertions(+), 1 deletion(-) diff --git a/TEST b/TEST index b5f5526..4d6e2b7 100644 --- a/TEST +++ b/TEST @@ -19130,7 +19130,7 @@ PASS XSLTFunctions_DocumentFunctionNoArg [Mixed] Actual output: MSFT_Conformance_Tests/XSLTFunctions/XSLTFunctions_DocumentFunctionNoArg.xuriella FAIL XSLTFunctions_DocumentFunctionWithAbsoluteArgument [Mixed]: There is no applicable method for the generic function - # + # when called with arguments (:DEFAULT-NAVIGATOR NIL diff --git a/xslt.lisp b/xslt.lisp index 674452e..036c267 100644 --- a/xslt.lisp +++ b/xslt.lisp @@ -52,7 +52,20 @@ (defun xslt-error (fmt &rest args) (error 'xslt-error :format-control fmt :format-arguments args)) +;; Many errors in XSLT are "recoverable", with a specified action that must +;; be taken if the error isn't raised. My original plan was to implement +;; such issues as continuable conditions, so that users are alerted about +;; portability issues with their stylesheet, but can contiue anyway. +;; +;; However, our current test suite driver compares against Saxon results, +;; and Saxon recovers (nearly) always. So our coverage of these errors +;; is very incomplete. +;; +;; Re-enable this code once we can check that it's actually being used +;; everywhere. (defun xslt-cerror (fmt &rest args) + (declare (ignore fmt args)) + #+(or) (with-simple-restart (recover "recover") (error 'recoverable-xslt-error :format-control fmt -- 2.11.4.GIT