On Mon, Apr 04, 2011 at 11:18:26AM -0700, Philip Guenther wrote: > On Mon, Apr 4, 2011 at 11:06 AM, Pascal Stumpf <[email protected]> wrote: > > pcc currently only chokes on some inline functions that need external > > linkage. gcc isn't pesky about that, but pcc and clang are (rightfully, > > imo). > > It's completely legal and defined (by the standard and not just gcc!) > for a function to be inline in the file where it's defined and have > external linkage. That just means "inline if you can in this file, > but still provide a copy callable from other files". Not if it's never declared as extern, according to the standard. In that case it's an "inline definition", as they call it.
> That's exactly > the semantic we want for pf_addr_compare(). If pcc or clang are > complaining about it they're broken or their warning settings are > misset. > > > Philip Guenther
