From: Simon Huggins <huggie@earth.li>
To: linux-kernel@vger.kernel.org
Cc: twaugh@redhat.com
Subject: Re: kernel-doc minor fix
Date: Sun, 17 Dec 2000 17:22:37 +0100 [thread overview]
Message-ID: <20001217172237.F1301@paranoidfreak.freeserve.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.10.10012161636480.10851-100000@virtualro.ic.ro>
In-Reply-To: <Pine.LNX.4.10.10012161636480.10851-100000@virtualro.ic.ro>; from jani@virtualro.ic.ro on Sat, Dec 16, 2000 at 04:41:44PM +0200
On Sat, Dec 16, 2000 at 04:41:44PM +0200, Jani Monoses wrote:
> --- /usr/src/linux/scripts/kernel-doc Tue Dec 12 11:25:59 2000
> +++ kernel-doc Sat Dec 16 15:53:17 2000
> @@ -664,10 +664,11 @@
> ##
> # takes a function prototype and spits out all the details
> -# stored in the global arrays/hsahes.
> +# stored in the global arrays/hashes.
> sub dump_function {
> my $prototype = shift @_;
> + $prototype =~ s/^const+ //;
> $prototype =~ s/^static+ //;
> $prototype =~ s/^extern+ //;
> $prototype =~ s/^inline+ //;
Since when did C accept constttttttttttttttttttt and staticcccccccc?
etc.
Should that be " +" not "+ " or is someone just trying to confuse me?
Or did someone try to mean s/foo//g by adding a +?
Yours confusedly,
Simon.
--
[ "Therapy is expensive. Popping bubble wrap is cheap. You choose." ]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-18 8:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-16 14:41 Jani Monoses
2000-12-17 16:22 ` Simon Huggins [this message]
2000-12-18 9:04 ` Jani Monoses
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=20001217172237.F1301@paranoidfreak.freeserve.co.uk \
--to=huggie@earth.li \
--cc=linux-kernel@vger.kernel.org \
--cc=twaugh@redhat.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
all inboxes | Powered by JetHome®