It does not stop the XML:: Checker, so it will continue looking for other errors.
The error message is created with XML:: Checker::error_string().
(The codes are still subject to change, as well the error descriptions.) Most errors have a link to the appropriate Validaty Constraint (VC) or other section in the XML specification.
XML:: Checker can be easily plugged into your application.
You can define your own fail handler in two ways, locally and globally.
Use a local variable to temporarily override the fail handler.
It uses mostly the same style of event handlers (or callbacks) as XML:: Parser. Currently, the XML:: Checker object is a blessed hash with the following (potentially useful) entries: This section is only interesting when using XML:: Checker directly.
This means that in XML:: DOM:: Val Parser no Text nodes are created for insignificant whitespace.Regardless of whether the Skip Insignif WS options is set, XML:: Checker always keeps track of whether whitespace is insignificant.After making a call to XML:: Checker's Char handler, you can find out if it was insignificant whitespace by calling the is Insignif WS method.This way the default fail handler is restored when the local variable goes out of scope, esp. The fail handler is called with the following parameters ($code, $msg, @context), where $code is the error code, $msg is the error description and @context contains information on where the error occurred.The @context is a (ordered) list of (key,value) pairs and can easily be turned into a hash.