| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
A slightly stronger version of Dialyzer discovered that various clauses
in the code of `xmerl` are unreachable. This code was commented out;
There is little reason to have code bloat that simply causes confusion.
An alternative change would be to simply delete this code.
|
|
|
|
|
|
Removes the built-in definitions of http://www.w3.org/2001/xml.xsd from
the xmerl_xsd module. xmerl_xsd does load the definitions of the above
schema into its processing table during initialization. This leads to
the inability to process XSD schemas that properly import xml.xsd (as
suggested in xml.xsd itself).
Furthermore, the definitions are loaded from a binary containing the
corresponding terms in Erlang external term format. Since this is not
refactoring safe the intended functionality already broke long ago
(prior to github import) because some of the record definitions did
change in releases older than R13B03.
To sum up, the current code does not do anything useful because the
built-in definitions from the binary can't be used due to incompatible
records. Thus, this fix is not backwards incompatible. The change also
adds two new test cases covering common use-cases when using 'xml:'
types in custom schemas.
|
|
|
|
Replace sloppy calls to io:format() in xmerl to use error_logger or debug
macros instead, as appropriate.
|
|
|
|
|
|
|
|
|
|
Add flag {comments, Flag} to xmerl_scan for filtering of comments.
Default (true) is that xmlComment records are returned from the scanner
and this flag should be set to false if one don't want comments
in the output.
Fix some bugs to get the test cases to run clean.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
warnings/errors in man pages
|
|
|
|
|
