From: "David S. Miller" <davem@redhat.com>
To: "Steve Grubb" <ddata@gate.net>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: asm/unistd.h
Date: Thu, 5 Apr 2001 08:45:07 -0700 (PDT) [thread overview]
Message-ID: <15052.37635.264641.436756@pizda.ninka.net> (raw)
In-Reply-To: <001701c0bde4$59825240$871a24cf@master>
In-Reply-To: <001701c0bde4$59825240$871a24cf@master>
Steve Grubb writes:
> It would seem to me that after hearing how the macros are used in practice,
> wouldn't turning them into inline functions be an improvement? This is
> something gcc supports, it accomplishes the same thing, and has the added
> advantage of type checking.
> http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_4.html#SEC92
Two reasons:
1) Sometimes I don't want any type checking because it would create
the necessity of adding a new include to a file --> a circular
dependency to resolve. Macros hide the types except in the
cases where they are actually invoked :-)
2) Historically GCC was very bad with code generation with inline
functions, so at that time the GCC manual statement "inline
functions are just like a macro" was technically false :-)
Yes, I know this is much different in today's gcc tree, but
there hasn't been a gcc release in over 2 years so...
Later,
David S. Miller
davem@redhat.com
next prev parent reply other threads:[~2001-04-05 15:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-05 15:23 asm/unistd.h Steve Grubb
2001-04-05 15:41 ` asm/unistd.h Bart Trojanowski
2001-04-05 15:45 ` David S. Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-04-05 12:58 asm/unistd.h Sardañons, Eliel
2001-04-05 13:06 ` asm/unistd.h Bart Trojanowski
2001-04-05 13:12 ` asm/unistd.h Tim Waugh
2001-04-05 14:26 ` asm/unistd.h Joseph Carter
2001-04-05 14:35 ` asm/unistd.h Bart Trojanowski
2001-04-05 14:35 ` asm/unistd.h Stephen Thomas
2001-04-05 14:45 ` asm/unistd.h Andreas Schwab
2001-04-05 17:38 ` asm/unistd.h J . A . Magallon
2001-04-05 13:07 ` asm/unistd.h David S. Miller
2001-04-05 13:13 ` asm/unistd.h Ben Collins
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=15052.37635.264641.436756@pizda.ninka.net \
--to=davem@redhat.com \
--cc=ddata@gate.net \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®