From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Vegard Nossum <vegard.nossum@gmail.com>
Cc: Sam Ravnborg <sam@ravnborg.org>, Adrian Bunk <bunk@kernel.org>,
linux-kbuild@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] headerdep: a tool for detecting inclusion cycles in header file
Date: Sat, 26 Apr 2008 16:59:19 +0300 [thread overview]
Message-ID: <48133537.7040800@cs.helsinki.fi> (raw)
In-Reply-To: <20080426134554.GA20727@damson.getinternet.no>
Hi Vegard,
Vegard Nossum wrote:
> @@ -0,0 +1,143 @@
> +#! /usr/bin/perl
> +#
> +# Detect cycles in the header file dependency graph
> +# Vegard Nossum <vegardno@ifi.uio.no>
> +#
> +
> +use strict;
> +use warnings;
> +
> +my @I = ('include');
> +my %deps = ();
> +
> +my @headers = grep { strip($_) } @ARGV;
> +
> +parse_all(@headers);
> +
> +detect_cycles(@headers);
> +#graph();
[snip]
> +exit;
> +# Output dependency graph in GraphViz language.
> +sub graph {
Shouldn't there be a command line option for printing out the GraphViz
files?
next prev parent reply other threads:[~2008-04-26 14:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-26 13:45 [PATCH] headerdep: a tool for detecting inclusion cycles in header file Vegard Nossum
2008-04-26 13:59 ` Pekka Enberg [this message]
2008-04-26 14:17 ` Vegard Nossum
2008-04-26 14:22 ` Nick Andrew
2008-04-26 18:03 ` Jan Engelhardt
2008-04-26 15:00 ` Adrian Bunk
2008-04-26 15:21 ` Julia Lawall
2008-04-26 15:30 ` Vegard Nossum
2008-04-26 15:25 ` Vegard Nossum
2008-04-26 16:17 ` Matthew Wilcox
2008-04-26 16:38 ` Adrian Bunk
2008-04-30 17:57 ` "Anyone who likes complexity and fuzzy logic" (Re: [PATCH] headerdep:...) Oleg Verych
2008-04-30 17:38 ` Matthew Wilcox
2008-04-26 16:44 ` [PATCH] headerdep: a tool for detecting inclusion cycles in header file Adrian Bunk
2008-04-26 16:57 ` Vegard Nossum
2008-04-26 17:23 ` Adrian Bunk
2008-04-26 17:55 ` Vegard Nossum
2008-04-26 18:11 ` Jan Engelhardt
2008-04-26 18:26 ` Sam Ravnborg
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=48133537.7040800@cs.helsinki.fi \
--to=penberg@cs.helsinki.fi \
--cc=bunk@kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=vegard.nossum@gmail.com \
/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