9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Steve Simon" <steve@quintile.net>
To: 9fans@9fans.net
Subject: [9fans] diff3 for c source
Date: Wed,  6 Oct 2010 09:33:44 +0100	[thread overview]
Message-ID: <055d170589876fa7a5e9cbc3c77c1954@quintile.net> (raw)

Anyone know of a tool that works like diff3 but has a fairly deep
knowledge of C cyntax, so it can merge changes at the C token level rather
than at the line level?

The problem I am trying to solve is keeping the (say) 9vx source in sync with
the plan9 kernel.

alternatively anyone known know of somthing which might be able to modify
the plan9 source to make it acceptable to gcc

	• adding names for unused function parameters
	• adding names for blind structure members
	• adding apropriate names for "auto structure member selection based on type"

the ed technique russ used is neat, and diff3 (v7 diff3 in my contrib) could do a
little better, but a real solution still eludes me.

-Steve



             reply	other threads:[~2010-10-06  8:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-06  8:33 Steve Simon [this message]
2010-10-06  9:14 ` yy
2010-10-06 10:23   ` Steve Simon

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=055d170589876fa7a5e9cbc3c77c1954@quintile.net \
    --to=steve@quintile.net \
    --cc=9fans@9fans.net \
    /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).