Merge pull request #76 from esl/fix_llvm19

Fix llvm19 builds

exml:parse/2 in case of error returns binary for consistency with oth…

…er APIs

Merge pull request #75 from esl/type_improvements

Type improvements

Fix CI build status link

Merge pull request #69 from esl/modernise

Modernise

Merge pull request #68 from esl/max-element-size

Fix and improve the check for maximum element size

Merge pull request #67 from esl/bugfix/subelement_with_name_and_ns

Fix subelement_with_name_and_ns bug #38

Merge pull request #66 from esl/to_iolist_types

Accept more xml types in to_iolist

Merge pull request #65 from esl/fix-null

Throw exception on null characters

Any further data passed via exml_stream:parse/2 to the parser won't be processed as well because rapidxml works on null-terminated strings and treats the whole input as empty. The similar issue happens when null character is in the middle of input (other exception is thrown but it has eof flag as well).

I implemented the fix that checks (in advance) whether the buffer contains null character. If so, it throws the error immediately. This way we can make sure that input received from Erlang will be valid in term of processing.

Merge pull request #63 from esl/xml_compliance

Verify forbidden chars inside cdata and escaped chars!