Re: [dmidecode] Dmidecode 2.6 to be released soon

[Petter Reinholdtsen]

[Jean Delvare]
>> -static inline int anchor_match(const struct bios_entry *entry, const char 
>> *p)
>> +static int anchor_match(const struct bios_entry *entry, const char *p)
>
> Oh well, this is the second time a problem is reported with this
> "inline" (first one being a compilation warning on BeOS, which I got
> rid of by not using -pedantic anymore).

I believe the problem is the order of the statements.  'inline static
int' work, 'static inline int' does not.

But 'inline' is just a compiler hint, and will be ignored if the
compiler find it useful.  And functions might be inlined anyway if the
compiler find that useful, so I suspect the 'inline' part is
completely useless. :)

> That being said, I am quite surprised that this "inline" causes that
> much trouble. I thought it was a standard keyword.

It is.  But it need to be used in a standard way. :)