All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Triplett <josh@freedesktop.org>
To: Christopher Li <sparse@chrisli.org>
Cc: linux-sparse@vger.kernel.org
Subject: Re: [PATCH] delay removing file scope
Date: Mon, 04 Dec 2006 18:04:10 -0800	[thread overview]
Message-ID: <4574D39A.9000703@freedesktop.org> (raw)
In-Reply-To: <20061130101608.GB27500@chrisli.org>

[-- Attachment #1: Type: text/plain, Size: 489 bytes --]

Christopher Li wrote:
> Sparse only returns the used symbol. By the time it return
> the symbol, it already destroyed the file scope.
> 
> This patch preserve the file scope. The caller can
> examine the unused symbols. e.g. If I want to generate
> ctags base on sparse, it need those unused symbols.

Merged, thanks.  I look forward to seeing your sparse-based ctags generator; a
ctags which actually *parses C* would provide significant improvements. :)

- Josh Triplett



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

      reply	other threads:[~2006-12-05  2:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-30 10:16 [PATCH] delay removing file scope Christopher Li
2006-12-05  2:04 ` Josh Triplett [this message]

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=4574D39A.9000703@freedesktop.org \
    --to=josh@freedesktop.org \
    --cc=linux-sparse@vger.kernel.org \
    --cc=sparse@chrisli.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.