git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Arlott <simon@fire.lp0.eu>
To: Paul Eggert <eggert@CS.UCLA.EDU>
Cc: Matthew Wilcox <matthew@wil.cx>, Denis Cheng <crquan@gmail.com>,
	kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
	git@vger.kernel.org
Subject: Re: diffutils: C labels misdetected as functions
Date: Sun, 22 Jul 2007 20:16:23 +0100	[thread overview]
Message-ID: <46A3AD07.1070504@simon.arlott.org.uk> (raw)
In-Reply-To: <87abtogu6u.fsf@penguin.cs.ucla.edu>

On 22/07/07 19:38, Paul Eggert wrote:
> Simon Arlott <simon@fire.lp0.eu> writes:
> 
>> The patch below stops diffutils treating C labels starting in column 1 as function names.
> 
> That patch alone wouldn't suffice, since -p is documented as implying
> -F '^[[:alpha:]$_]'.  If the behavior changes, we'd also have to
> change the documentation to match.

Ok.

> I'm not sure the change is a good idea.  It would complicate the
> documentation and therefore the user interface, without that much

Complicated documentation means a bug shouldn't be fixed?

> benefit.  And it wouldn't suffice in general, since it would still
> mishandle labels followed by comments or by white space.

Yes, the regexp needs changing further to ignore comments...

"[[:alpha:]$_][^:]*$" perhaps? Although that ignores functions with
comments on the same line containing a :.

> Also, for long C functions some people might rather see a top-level
> (unindented) label highlighted than the function name highlighted, so
> they might prefer the current behavior.

"-p  --show-c-function  Show which C function each change is in."

It's not "--show-c-function-or-label".

> Anyway, to work around your problem without changing "diff", you can
> use "diff -u -F '^[[:alpha:]$_](|.*[^:])$'" instead of "diff -u -p".

Perhaps git could do this (or similar) as a workaround? (Cc:ed)

> Or you can put a single space before the labels in question: they'll
> still stand out plenty.

The code should definitely not need to be modified to work around a
diff bug.

-- 
Simon Arlott

       reply	other threads:[~2007-07-22 19:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1184489571313-git-send-email-crquan@gmail.com>
     [not found] ` <4699EEA9.6070709@simon.arlott.org.uk>
     [not found]   ` <20070720170743.GF14791@parisc-linux.org>
     [not found]     ` <46A0F282.8070103@simon.arlott.org.uk>
     [not found]       ` <20070720180019.GJ14791@parisc-linux.org>
     [not found]         ` <46A1A375.3020900@simon.arlott.org.uk>
     [not found]           ` <20070721135200.GQ14791@parisc-linux.org>
     [not found]             ` <46A25BE0.7000104@simon.arlott.org.uk>
     [not found]               ` <87abtogu6u.fsf@penguin.cs.ucla.edu>
2007-07-22 19:16                 ` Simon Arlott [this message]
2007-07-22 21:30                   ` diffutils: C labels misdetected as functions Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46A3AD07.1070504@simon.arlott.org.uk \
    --to=simon@fire.lp0.eu \
    --cc=crquan@gmail.com \
    --cc=eggert@CS.UCLA.EDU \
    --cc=git@vger.kernel.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew@wil.cx \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).