Added an optional verbose error output for encoding of required fields. Added a function for enabling said verbosity, akin to set_strict(). Should be no changes to default behaviour.
Field outputs are ordered by field->number, except for sub-messages (or similar fields) that appear at the end of the list, regardless of field->number. This could be overcome in a hackish way by parsing the output stream prior to returning it on depth==1 and manually ordering things? I can live without having to do that in C++.
Has been tested with:
All "standard" fields.
oneofrepeatedsub-messages
Added an optional verbose error output for encoding of required fields. Added a function for enabling said verbosity, akin to set_strict(). Should be no changes to default behaviour.
Field outputs are ordered by
field->number
, except for sub-messages (or similar fields) that appear at the end of the list, regardless offield->number
. This could be overcome in a hackish way by parsing the output stream prior to returning it ondepth==1
and manually ordering things? I can live without having to do that in C++.Has been tested with: All "standard" fields.
oneof
repeated
sub-messages
This should fix #93, @tsaubergine.