Hi Pablo, On Sun, Feb 09, 2020 at 11:21:43PM +0100, Pablo Neira Ayuso wrote: [...] > Yes, I don't expect mid-string matching in the future, but you never > know, so better reserve this just in case :-) DONE, please see v2 I just sent. > > BTW: Given how confusing bison-generated error messages are, maybe I > > should introduce "infixasteriskstring" in scanner.l to catch unescaped > > infix asterisks and generate a readable error message from there? > > bison syntax error reporting is not great, yes. If you think that > makes it easier for error reporting as a short term way to address the > issue, that's fine with me. Tried, but didn't go well - proper error reporting is best put into parser_bison, but there one can't complain about mid-string asterisk "anywhere" but only in defined places. So in others the then known token will make error messages even more confusing. Cheers, Phil
