From owner-freebsd-current Fri Mar 13 15:16:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA07523 for freebsd-current-outgoing; Fri, 13 Mar 1998 15:16:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ocean.campus.luth.se (ocean.campus.luth.se [130.240.194.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA07513 for ; Fri, 13 Mar 1998 15:16:05 -0800 (PST) (envelope-from karpen@ocean.campus.luth.se) Received: (from karpen@localhost) by ocean.campus.luth.se (8.8.8/8.8.8) id AAA20821; Sat, 14 Mar 1998 00:11:00 +0100 (CET) (envelope-from karpen) From: Mikael Karpberg Message-Id: <199803132311.AAA20821@ocean.campus.luth.se> Subject: Re: A question about sys/sys/queue.h In-Reply-To: <199803131808.LAA15797@pluto.plutotech.com> from "Justin T. Gibbs" at "Mar 13, 98 11:05:32 am" To: gibbs@plutotech.com (Justin T. Gibbs) Date: Sat, 14 Mar 1998 00:11:00 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Justin T. Gibbs: > Actually, inline functions will not work for the queue macros unless you > change the way you specify the "links" portion of the object. I agree > that, in general, using an inline is better than using a macro. Just FYI. Inline functions also result in non-inlined code when compiling with -g. Also, inlines should be declared "static inline" to act as "real inlines" in gcc. I was rather stunned when I was pointed to gcc info pages about this, when I was trying to argue that "static" was completely useless to add to inline functions. I was proved wrong, for gcc inlines. I haven't checked, but I would think g++ generates "real inlines" without the "static" keyword. /Mikael To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message