>
> - The Zorba_SerializerOptions are also used in the C API.
>
Do you mean the C++ API, or literally the C API? I don't recall it in
XQC... (relevant because I'd like to have it throw exceptions for bad
values)
If you mean "don't make any backwards-incompatible changes", then yes,
understood - my intent is to eliminate the internal redundancy and leave
the existing public API as it is.
- The encodings parameter should be an arbitrary string to allow for more
> encodings than utf8 and utf816.
This would be a backwards-incompatible change, most likely, and so would
have to wait for Zorba 3.0.
> rOptions are also used in the C API.
> - The Zorba_Serialize
>
Do you mean the C++ API, or literally the C API? I don't recall it in
XQC... (relevant because I'd like to have it throw exceptions for bad
values)
If you mean "don't make any backwards- incompatible changes", then yes,
understood - my intent is to eliminate the internal redundancy and leave
the existing public API as it is.
- The encodings parameter should be an arbitrary string to allow for more
> encodings than utf8 and utf816.
This would be a backwards- incompatible change, most likely, and so would
have to wait for Zorba 3.0.