[bug #64016] Simplify update_goal_chain.

Follow-up Comment #5, bug #64016 (project make): This made me think, why don't we also test the opposite situation? That's that in the sequential mode make does not advance to the next target, until the current target is finished. diff --git a/tests/scripts/features/double_colon b/tests/scripts/

[bug #64016] Simplify update_goal_chain.

Follow-up Comment #4, bug #64016 (project make): [comment #2 comment #2:] > I don't understand the test that was added though. How does this test show that both rules are run at the same time? It seems like it would behave the same even if they were not. Indeed. My test was lacking necessary sy

[bug #64016] Simplify update_goal_chain.

Update of bug #64016 (project make): Status:None => Fixed Open/Closed:Open => Closed Fixed Release:None => SCM Triage Status:

[bug #64016] Simplify update_goal_chain.

Follow-up Comment #2, bug #64016 (project make): I installed the code cleanup, thanks. I don't understand the test that was added though. How does this test show that both rules are run at the same time? It seems like it would behave the same even if they were not. Don't you mean something lik

[bug #64016] Simplify update_goal_chain.

Follow-up Comment #1, bug #64016 (project make): These two small patches modify update_goal_chain to 1. avoid double negation. 2. avoid a redundant ternary operator. Make's behavior is intact. ___ Reply to this item at:

[bug #64016] Simplify update_goal_chain.

Additional Item Attachment, bug #64016 (project make): File name: sv64016_part1.diff Size:2 KB File name: sv64016_part2.diff Size:0 KB

[bug #64016] Simplify update_goal_chain.

URL: Summary: Simplify update_goal_chain. Group: make Submitter: dgoncharov Submitted: Sat 08 Apr 2023 03:55:58 AM UTC Severity: 3 - Normal Item Group: Enhanceme