diff options
| author | Andy Polyakov <appro@openssl.org> | 2007-07-30 11:42:08 +0000 |
|---|---|---|
| committer | Andy Polyakov <appro@openssl.org> | 2007-07-30 11:42:08 +0000 |
| commit | 1891f5b395038901ab05c54e82367cea44a3f846 (patch) | |
| tree | a8bee948f8cd8e0558d9a55840db951d7cfdb515 /crypto/stack | |
| parent | a3963619f64377e5de7418c09bece61f8389b3fc (diff) | |
| download | openssl-1891f5b395038901ab05c54e82367cea44a3f846.tar.gz | |
As for inline vs. __inline. The original code implies that most compilers
understand inline, while WIN32 ones insist on __inline. Well, there are
other compilers that insist on __inline. At the same time it turned out
that most compilers understand both __inline and inline. I could find
only one that doesn't understand __inline, Sun C. In other words it seems
that __inline as preferred choice provides better coverage...
Diffstat (limited to 'crypto/stack')
| -rw-r--r-- | crypto/stack/safestack.h | 13 |
1 files changed, 8 insertions, 5 deletions
diff --git a/crypto/stack/safestack.h b/crypto/stack/safestack.h index a2b0287217..f24353b131 100644 --- a/crypto/stack/safestack.h +++ b/crypto/stack/safestack.h @@ -60,11 +60,14 @@ #ifndef OPENSSL_ALLOW_FCAST #ifndef OPENSSL_INLINE -#ifdef OPENSSL_SYSNAME_WIN32 -#define OPENSSL_INLINE __inline static -#else -#define OPENSSL_INLINE inline static -#endif +# if defined(__SUNPRO_C) +# if __SUNPRO_C>0x520 +# define __inline inline +# else +# define __inline +# endif +# endif +# define OPENSSL_INLINE __inline static #endif #define STACK_OF(type) struct stack_st_##type |