|
|
DescriptionAvoid some FX_BOOL/bool noise in fx_codec_fax.cpp
NEXTBIT() is particularly pernicious in that it isn't syntactically
an expression, but rather two expressions. Replace it with an inline
along the way.
Committed: https://pdfium.googlesource.com/pdfium/+/1842be87408b06bf0b4c521044c09452caac5c80
Patch Set 1 #Patch Set 2 : remove locals #Patch Set 3 : Even simpler #Patch Set 4 : remove local #Messages
Total messages: 20 (15 generated)
The CQ bit was checked by tsepez@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Description was changed from ========== Avoid some FX_BOOL/bool noise in fx_codec_fax.cpp NEXTBIT() is particularly pernicious in that it isn't syntactically an expression, but rather two expressions. Replace it with an inline along the way. ========== to ========== Avoid some FX_BOOL/bool noise in fx_codec_fax.cpp NEXTBIT() is particularly pernicious in that it isn't syntactically an expression, but rather two expressions. Replace it with an inline along the way. ==========
tsepez@chromium.org changed reviewers: + npm@chromium.org, weili@chromium.org
npm, see https://build.chromium.org/p/tryserver.client.pdfium/builders/win_xfa/builds/... for context on how this blocks fx_bool conversion.
The CQ bit was checked by tsepez@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
The CQ bit was checked by tsepez@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was checked by tsepez@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
lgtm. You could also change the FX_BOOL to bool right away. Not sure how long we'll keep having FX_BOOL as int for.
On 2016/10/26 17:17:58, npm wrote: > lgtm. You could also change the FX_BOOL to bool right away. > Not sure how long we'll keep having FX_BOOL as int for. Acknowledged. There are ~7K lines containing FX_BOOL, I'd assumed they'd get flipped via sed rather than one at a time by hand once we tidy the underlying mismatches. We were stymied on this for a while due to silent breakage when we flipped these; but the win_xfa bot has compilation flags to spot most of these now ...
The CQ bit was unchecked by tsepez@chromium.org
The CQ bit was checked by tsepez@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Message was sent while issue was closed.
Description was changed from ========== Avoid some FX_BOOL/bool noise in fx_codec_fax.cpp NEXTBIT() is particularly pernicious in that it isn't syntactically an expression, but rather two expressions. Replace it with an inline along the way. ========== to ========== Avoid some FX_BOOL/bool noise in fx_codec_fax.cpp NEXTBIT() is particularly pernicious in that it isn't syntactically an expression, but rather two expressions. Replace it with an inline along the way. Committed: https://pdfium.googlesource.com/pdfium/+/1842be87408b06bf0b4c521044c09452caac... ==========
Message was sent while issue was closed.
Committed patchset #4 (id:60001) as https://pdfium.googlesource.com/pdfium/+/1842be87408b06bf0b4c521044c09452caac... |