Fred wrote:
> > if that's what you want, maybe you could start by
> > putting the INLINE stuff back again? <halfwink>
>
> I could not see the value in the inline stuff that configure was
> setting up, and still don't.
the INLINE stuff guarantees that "inline" is defined to be
whatever directive the compiler uses for explicit inlining.
quoting the autoconf docs:
If the C compiler supports the keyword inline,
do nothing. Otherwise define inline to __inline__
or __inline if it accepts one of those, otherwise
define inline to be empty
as a result, you can always use "inline" in your code, and
have it do the right thing on all compilers that support ex-
plicit inlining (all modern C compilers, in practice).
:::
to deal with people compiling Python with a C compiler, but
linking it with a C++ compiler, the config.h.in file could be
written as:
/* Define "inline" to be whatever the C compiler calls it.
To avoid problems when mixing C and C++, make sure
to only use "inline" for internal interfaces. */
#ifndef __cplusplus
#undef inline
#endif
</F>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4