From: Rusty Russell <rusty@rustcorp.com.au>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Brian King <brking@us.ibm.com>,
akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: Question on MODULE_VERSION macro
Date: Thu, 26 Feb 2004 12:50:37 +1100 [thread overview]
Message-ID: <20040226023341.42E862C270@lists.samba.org> (raw)
In-Reply-To: Your message of "Wed, 25 Feb 2004 22:36:59 BST." <20040225213659.GA9985@mars.ravnborg.org>
In message <20040225213659.GA9985@mars.ravnborg.org> you write:
> Hi Rusty.
>
> I have not yet fully understood why you want to parse every source file.
> I can see in the implemntation that you only calculate the sum of
> code-lines, and not comments.
> But why do we want to add this complexity - compared to just
> calculating the sum of the whole file?
> If the calculated sum is being presented as based on the source code
> I assume people can understand that the sum does not match even after
> updating a comment.
The strongest example is that Andrew Morton always "fixes" whitespace
as patches go through his tree. It's about 50 lines of code, and it's
not slow (but has definite room for optimization).
> The current implementation fails to locate include files in the local
> directory when compiled using "make O=...".
There's no documentation I could find for "O=", BTW. I'm not even
sure what it does...
> This is due to the fact that some files are present in the _deps
> file with full path, others with relative path.
Right. 8(
> My next question. Since we only parse a subset of the headers, is it
> really needed to parse any of them?
> My thinking is that we should either:
> a) parse all header files (except those marked with $(wildcard))
> b) parse no header files.
I was thinking of the driver author. Driver consists of three .c
files, and a local .h file. They want to catch anyone touching any of
these files. But they don't want the sum to change just because
someone adds a new inline function to linux/kernel.h.
If it's impractical, we can just skip all the headers. But it would
be a real loss.
> > + cmd = malloc(strlen(objfile) + sizeof("..cmd"));
>
> You miss a "+ 1" to count for trailing '\0'.
Um, sizeof() vs strlen().
> > + len = strcspn(p, " \\\n");
> > + if (memcmp(objfile, p, dirlen) == 0) {
> > + char source[len + 1];
> gcc extension, you do not want to use malloc here?
Yeah, I love GCC. It's also in ISO C, BTW.
> > + printf("parsing %s\n", source);
> Debug printf - to be deleted.
Ack.
Thanks!
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
next prev parent reply other threads:[~2004-02-26 2:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040119214233.GF967@beaverton.ibm.com>
2004-01-20 0:57 ` Rusty Russell
2004-01-20 1:17 ` Greg KH
2004-01-20 7:47 ` Rusty Russell
2004-02-20 21:44 ` Brian King
2004-02-21 1:07 ` Rusty Russell
2004-02-22 23:23 ` Sam Ravnborg
2004-02-23 3:51 ` Rusty Russell
2004-02-23 21:17 ` Sam Ravnborg
2004-02-24 6:13 ` Rusty Russell
2004-02-25 21:36 ` Sam Ravnborg
2004-02-26 1:50 ` Rusty Russell [this message]
2004-02-26 7:12 ` Sam Ravnborg
2004-03-10 20:49 ` Brian King
2004-03-10 21:08 ` Greg KH
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=20040226023341.42E862C270@lists.samba.org \
--to=rusty@rustcorp.com.au \
--cc=akpm@osdl.org \
--cc=brking@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome