Add support for BYTE and CHAR to VARIANT #451
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add support for VT_UI1 and BYTE constructor. Another thing to consider is that UCHAR type which must match to "unsigned char" for VT_UI1, cant be set. Because bVal is of BYTE class while UCHAR is ancestor of BYTE. Can't assign to bVal UCHAR object instance. In this case it is not possible to make VARIANT(UCHAR value) constructor.
|
Corresponding tests? |
These are tests for constructor of variants of CHAR and BYTE
twall
added a commit
that referenced
this pull request
Aug 30, 2015
Add support for BYTE and CHAR to VARIANT
twall
added a commit
that referenced
this pull request
Aug 30, 2015
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Propose support for BYTE and CHAR type of VARIANT.