Re: clang 21.1.8 squawks about `/*` nested within "mbiter-aux.c" comment
Jeffrey Walton <[email protected]> Tue, 21 Jul 2026 10:21:30 -0400
| Newsgroups | gmane.comp.lib.gnulib.bugs |
|---|---|
| Message-ID | <CAH8yC8nnMg0wSqmGMGoJ9+5UqP8qg892koBsvvkVGk=Fjb-eTQ@mail.gmail.com> |
On Tue, Jul 21, 2026 at 8:09 AM Bruno Haible via Gnulib discussion list <[email protected]> wrote: > > Simon Josefsson wrote: > > > - to U+0100. (See libiconv/tests/*.TXT for all the mapping tables.) > > > + to U+0100. (See libiconv/tests/?*.TXT for all the mapping tables.) > > > > Ugh. > > Why? It's a working wildcard expression, that can be used like the one before: > $ grep '^0xC480' libiconv/tests/?*.TXT > $ grep '0x0100$' libiconv/tests/?*.TXT > > > How about > > > > - to U+0100. (See libiconv/tests/*.TXT for all the mapping tables.) > > + to U+0100. (See *.TXT in libiconv/tests/ for all the mapping tables.) > > > > instead? > > That would have been a workaround if I had not found something less intrusive. I think the question mark takes away from the aesthetics. It's not your fault since this seems like a dumb warning that needs an AI agent to tell the compiler it is not a problem. How about using a non-breaking space (nbsp) instead of a question mark? Jeff