Explicity use CFX_ByteStrings in a couple of places

Explicity use CFX_ByteStrings in a couple of places

These are exposed by making the ByteString from ByteStringC
ctor explicit, but we can clean them up independently.

Committed: https://pdfium.googlesource.com/pdfium/+/85fc26f3411584586707798c1ebf39a194f60cf0

[Tom Sepez, 2016-04-15 01:10:41]

Description was changed from

==========
Explicity use CFX_ByteStrings in a couple of places

These are exposed by making the ByteStringC ctor explicit, but
we can clean them up independently.
==========

to

==========
Explicity use CFX_ByteStrings in a couple of places

These are exposed by making the ByteString from ByteStringC
ctor explicit, but we can clean them up independently.
==========

[Tom Sepez, 2016-04-15 01:10:41]

tsepez@chromium.org changed reviewers:
+ thestig@chromium.org

[Tom Sepez, 2016-04-15 01:10:58]

For review.

[Lei Zhang, 2016-04-15 01:15:24]

lgtm

[Tom Sepez, 2016-04-15 01:16:31]

The CQ bit was checked by tsepez@chromium.org

[commit-bot: I haz the power, 2016-04-15 01:16:37]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1884363002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1884363002/1

[commit-bot: I haz the power, 2016-04-15 01:50:50]

Description was changed from

==========
Explicity use CFX_ByteStrings in a couple of places

These are exposed by making the ByteString from ByteStringC
ctor explicit, but we can clean them up independently.
==========

to

==========
Explicity use CFX_ByteStrings in a couple of places

These are exposed by making the ByteString from ByteStringC
ctor explicit, but we can clean them up independently.

Committed:
https://pdfium.googlesource.com/pdfium/+/85fc26f3411584586707798c1ebf39a194f6...
==========

[commit-bot: I haz the power, 2016-04-15 01:50:51]

Committed patchset #1 (id:1) as
https://pdfium.googlesource.com/pdfium/+/85fc26f3411584586707798c1ebf39a194f6...