On 2/18/07, Robert Shearman <[EMAIL PROTECTED]> wrote:
Joris Huizer wrote:
> Though the keyword "inline" implies the code should get inlined, and
> if it shouldn't, the implementation copy should be removed from the
> unicode.h file
No, it's a hint to the compiler. "static inline" says to the co
Joris Huizer wrote:
Though the keyword "inline" implies the code should get inlined, and
if it shouldn't, the implementation copy should be removed from the
unicode.h file
No, it's a hint to the compiler. "static inline" says to the compiler
try to inline this function if it is worth it, or o
Robert Shearman <[EMAIL PROTECTED]> wrote: Joris Huizer wrote:
> Hello,
>
> I was looking at the result of configuring with -ansi,
> -pedantic flags. It gives loads of warnings (not all
> relevant - also complaining about 'long long' not
> being ansi) and indicates unnamed unions, among other
> t
Joris Huizer wrote:
Hello,
I was looking at the result of configuring with -ansi,
-pedantic flags. It gives loads of warnings (not all
relevant - also complaining about 'long long' not
being ansi) and indicates unnamed unions, among other
things.
Could someone confirm my idea that unnamed unions
Hello,
I was looking at the result of configuring with -ansi,
-pedantic flags. It gives loads of warnings (not all
relevant - also complaining about 'long long' not
being ansi) and indicates unnamed unions, among other
things.
Could someone confirm my idea that unnamed unions must
all be dealt wit
