lkml.org 
[lkml]   [1996]   [Mar]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: Current Status
Date
> I think __inline__ will work because gcc uses it to escape ANSI.
> The point is that it will not conflict with POSIX identifiers.
> See what __inline__ does with Think C and Turbo C.

__ is important to hide compilerisms (like __builtin_vararg etc). If your
compiler only knows inline the #define __inline__ for it.

> When programs fail to compile with gcc -ansi, it means that the
> header file did not use #ifdef to remove inline functions and
> substitute library functions. It also means that to programmer
> is using something they should not: see the gcc man page.
> It tells you that -ansi does not check for ANSI compliance!
> Enable all the warnings instead, and maybe buy a proper tool.

Unless I am mistaken __* symbols are undefined and may be used by
compilers for funnies in ANSI code. gcc -ansi shouldnt go to library
functions .. thats foul.

Alan


\
 
 \ /
  Last update: 2005-03-22 13:36    [W:0.154 / U:0.060 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site