Skip to content

Conversation

@webcoyote
Copy link

Ensure that unpacker can skip extra fields of type Str8, Bin8, Bin16 and Bin32
which may be present when using PackerCompatibilityOptions.None

@webcoyote
Copy link
Author

This is rebased to the 0.5 branch because 0.6 is still in beta.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you want to specify regular ASCIIEncoding here? There are 2 minor problems:

  1. ASCIIEncoding.Default does NOT return ASCII encoding in many countriies (but they are usually compatible to ASCII for ascii charactors, so this is really trivial issue because String40 only contains ascii chars).
  2. ASCIIEncoding does not exist in WinRT, so this line breaks build.
    Since String40 has ASCII charactors only, so you can use Encoding.UTF8.GetBytes(String40) safely here.

@yfakariya
Copy link
Member

Thank you for your PR!
I'll merge it for 0.5 and 0.6 branch when you resolve a minor test code build issue.

Ensure that unpacker can skip extra fields of type Str8, Bin8, Bin16 and Bin32
which may be present when using PackerCompatibilityOptions.None
@webcoyote webcoyote force-pushed the fix-unpack-skipping branch from 6e75d76 to fd4c1b8 Compare August 5, 2015 17:10
@webcoyote
Copy link
Author

Thanks for the information about WinRT; I've corrected the issue you pointed out and changed ASCII -> UTF8.

yfakariya added a commit that referenced this pull request Aug 9, 2015
yfakariya added a commit that referenced this pull request Aug 9, 2015
This commit complements PR #98. ItemsUnpacker also missed ext type handling too.
@yfakariya yfakariya merged commit fd4c1b8 into msgpack:master Aug 9, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants