Thanks for the rapid response and proposal. I'd wanted to test yesterday but had to postpone.
On Mon, May 8, 2023 at 12:18 PM Claudio Jeker <[email protected]> wrote: > Here is a possible solution where a perfect match aborts the detection > loop. Now this only works if the labels are in the right order ("in" > before "invalid"). This is similar to what I had in mind, but shorter than what I'd thought of. I'll test on -current first and report back. After, I'll adapt for -release after (i.e. the equivalent of r1.124 for parser.c [1]). > I wonder if chaning "invalid" to "notvalid" or "noteligible" would be a > better fix for now... Personally, I like the flexibility of keyword freedom, given the small one-time price to pay of sorting. Sorting may make maintenance a little easier too; at least I've seen several recent commits elsewhere to that end. Best regards, Rogier
