From: dank@trellisinc.com
To: linux-kernel@vger.kernel.org
Cc: Eli Carter <eli.carter@inet.com>
Subject: Re: [PATCH] pcnet32 compilation fix for 2.4.3pre6
Date: Thu, 29 Mar 2001 16:09:25 -0500 (EST) [thread overview]
Message-ID: <20010329210925.3161C6E099@fancypants.trellisinc.com> (raw)
In-Reply-To: <3ABA15F7.6155F0EE@inet.com>
Eli Carter wrote:
> Hmm... I used __inline__ because the other function in the same
> headerfile used it... What is the difference between the two, and is
> one depricated now? (And what about in 2.2.x?)
the inline keyword was not added into the c language until the ansi/iso
c99 revision, echoing its use in c++. prior to that time, gcc supplied
__inline__ as a vendor extension simulating this behavior which could be
compiled without violating checks for strict ansi conformance.
with the new ansi standard, this use of __inline__ is no longer
necessary, although for gcc to grok it as legal ansi requires (iirc) the
macro _ISOC99_SOURCE_ must be defined.
--
nick black * head developer, trellis network security * www.trellisinc.com
"the tao gave birth to machine language. machine language gave birth to the
assembler. the assembler gave rise to the compiler. now there are ten
thousand languages. each has its place, but avoid cobol if you can." - ttop
next prev parent reply other threads:[~2001-03-29 21:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-22 6:38 Andrzej Krzysztofowicz
2001-03-22 10:43 ` Jeff Garzik
2001-03-22 13:40 ` Jeff Garzik
2001-03-22 14:39 ` Eli Carter
2001-03-22 14:46 ` Jeff Garzik
2001-03-22 15:10 ` Eli Carter
2001-03-22 16:23 ` Jeff Garzik
2001-03-29 21:09 ` dank [this message]
2001-03-29 21:25 ` Ulrich Drepper
2001-03-29 21:29 ` Eli Carter
2001-03-29 22:55 ` Tom Leete
2001-03-30 9:36 ` Jeff Garzik
2001-03-22 14:49 ` Alan Cox
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=20010329210925.3161C6E099@fancypants.trellisinc.com \
--to=dank@trellisinc.com \
--cc=eli.carter@inet.com \
--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®