Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 18 Jun 2002 10:21:34 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 18 Jun 2002 10:21:33 -0400 Received: from web13202.mail.yahoo.com ([216.136.174.187]:7713 "HELO web13202.mail.yahoo.com") by vger.kernel.org with SMTP id ; Tue, 18 Jun 2002 10:21:32 -0400 Message-ID: <20020618142133.53974.qmail@web13202.mail.yahoo.com> Date: Tue, 18 Jun 2002 07:21:33 -0700 (PDT) From: "X.Xiao" Subject: static inline vs. extern inline; inline vs. __inline__ To: linux-kernel@vger.kernel.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 859 Lines: 24 After seeing various 'static inline', 'extern inline', 'inline' and '__inline__' in the kernel source, and reading GCC's Inline subsection, it's still hard to use them in a clear way: 1. what's the key difference between 'static' and 'extern' for inline? is there a rule to pick which one during development(such as library or driver coding) 2. what's the difference between 'inline' and '__inline__'? I wish the answer were in FAQ but it's not. Thanks a lot! X.Xiao __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/