git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] Avoid false positives in label detection in cpp diff hunk header regex.

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 22, 2013, 22:32 UTC
Message-ID
<7vhak35ami.fsf@alter.siamese.dyndns.org>
In-Reply-To
<514CD34F.70107@kdbg.org>
Johannes Sixt <j6t@kdbg.org> writes:
Show 27 quoted lines
> Am 22.03.2013 16:02, schrieb Junio C Hamano:
>> Vadim Zeitlin <vz-git@zeitlins.org> writes:
>> 
>>> A C++ method start such as
>>>
>>>         void
>>>         foo::bar()
>>>
>>> wasn't recognized by cpp diff driver as it mistakenly included "foo::bar" as a
>>> label. However the colon in a label can't be followed by another colon, so
>>> recognize this case specially to correctly detect C++ methods using this style.
>
> Much appreciated!
>
>>>  PATTERNS("cpp",
>>>          /* Jump targets or access declarations */
>>> -        "!^[ \t]*[A-Za-z_][A-Za-z_0-9]*:.*$\n"
>>> +        "!^[ \t]*[A-Za-z_][A-Za-z_0-9]*:([^:].*$|$)\n"
>> 
>> Hmm.  Wouldn't "find a word (possibly after indentation), colon and
>> then either a non-colon or end of line" be sufficient and simpler?
>> iow, something like...
>> 
>>        "!^[ \t]*[A-Za-z_][A-Za-z_0-9]*:([^:]|$)"
>
> Yes, indeed. We don't need to match more than necessary in a negative
> pattern. The \n must still remain, though.

... because \n is not for matching against the text, but merely to separate the regular expressions, right?

I also wonder if 
	label :

should also be caught, or is it too weird format to be worth supporting?

Previous: Johannes SixtNext: Johannes Sixt
Message 5 of 9 in “Avoid false positives in label detection in cpp diff hunk header regex.”
  1. Avoid false positives in label detection in cpp diff hunk header regex.Vadim Zeitlin, Mar 22, 2013
  2. Junio C HamanoMar 22, 2013
  3. Vadim ZeitlinMar 22, 2013
  4. Johannes SixtMar 22, 2013
  5. Junio C HamanoMar 22, 2013
  6. Johannes SixtMar 22, 2013
  7. Vadim ZeitlinMar 23, 2013
  8. Andreas SchwabMar 23, 2013
  9. Vadim ZeitlinMar 23, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.