Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code | Sign in
(2329)

Issue 351880043: Issue 5485: avoid -Wsequence-point warning

Can't Edit
Can't Publish+Mail
Start Review
Created:
5 years, 1 month ago by Malte Meyn
Modified:
5 years, 1 month ago
Reviewers:
Valentin Villenave, dak
CC:
lilypond-devel_gnu.org
Visibility:
Public.

Description

Issue 5485: avoid -Wsequence-point warning

Patch Set 1 #

Patch Set 2 : Ouch. Didn’t test and forgot the ! #

Total comments: 1

Patch Set 3 : Make it (nearly) as efficient as it was before. #

Unified diffs Side-by-side diffs Delta from patch set Stats (+8 lines, -5 lines) Patch
M lily/page-turn-page-breaking.cc View 1 2 1 chunk +8 lines, -5 lines 0 comments Download

Messages

Total messages: 5
Malte Meyn
Ouch. Didn’t test and forgot the !
5 years, 1 month ago (2019-02-28 12:53:29 UTC) #1
Valentin Villenave
Greetings Malte, nice catch! I’d been struggling with it for a while. I believe that’s ...
5 years, 1 month ago (2019-02-28 13:08:32 UTC) #2
dak
https://codereview.appspot.com/351880043/diff/20001/lily/page-turn-page-breaking.cc File lily/page-turn-page-breaking.cc (right): https://codereview.appspot.com/351880043/diff/20001/lily/page-turn-page-breaking.cc#newcode37 lily/page-turn-page-breaking.cc:37: bool page_breakable = scm_is_symbol (g->get_property ("page-break-permission")); This always looks ...
5 years, 1 month ago (2019-02-28 13:19:11 UTC) #3
Malte Meyn
Make it (nearly) as efficient as it was before.
5 years, 1 month ago (2019-02-28 14:22:35 UTC) #4
Malte Meyn
5 years, 1 month ago (2019-02-28 14:25:26 UTC) #5
On 2019/02/28 14:22:35, Malte Meyn wrote:
> Make it (nearly) as efficient as it was before.

“nearly” because (!line_breakable || !page_breakable) might need only the
line_breakable lookup. But I thought we have enough “if”s here already …
Sign in to reply to this message.

Powered by Google App Engine
RSS Feeds Recent Issues | This issue
This is Rietveld f62528b