gperf - Patches: patch #9561, Fix always-true subexpression in...
You are not allowed to post comments on this tracker with your current authentication level.
patch #9561: Fix always-true subexpression in step 4 of Search::find_positions()
Submitter: | Frank Wojcik <fwojcik> | ||
Submitted: | Sat 10 Feb 2018 12:52:51 AM UTC | ||
Category: | None | Priority: | 5 - Normal |
Status: | Done | Privacy: | Public |
Assigned to: | haible | Open/Closed: | Closed |
Sat 08 Sep 2018 01:57:49 PM UTC, comment #1: |
Bruno Haible <haible> |
Sat 10 Feb 2018 12:52:51 AM UTC, original submission:
Step 4 of Search::find_positions() contains an expression which is always true. Because the for loop makes i3 always be >=0:
|
Frank Wojcik <fwojcik> |
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 4 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2018-09-08 | haible | Status | None | Done | |
Assigned to | None | haible | |||
Open/Closed | Open | Closed | |||
2018-02-10 | fwojcik | Attached File | - | Added alwaystrue.diff, #43224 |
Powered by Savane 3.13-4448.
Corresponding source code
Thanks for the report. Yes, your guess was good. But the intent was also that i3 could be -1 (= LASTCHAR).