Commit 1891f5b3 authored by Andy Polyakov's avatar Andy Polyakov
Browse files

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...
parent a3963619

crypto/stack/safestack.h

+8 −5
Original line number Diff line number Diff line
@@ -60,11 +60,14 @@ 
#ifndef OPENSSL_ALLOW_FCAST



#ifndef OPENSSL_INLINE

#ifdef OPENSSL_SYSNAME_WIN32

#define OPENSSL_INLINE __inline static

# if defined(__SUNPRO_C)

#  if __SUNPRO_C>0x520

#    define __inline inline

#  else

#define OPENSSL_INLINE inline static

#    define __inline

#  endif

# endif

# define OPENSSL_INLINE __inline static

#endif



#define STACK_OF(type) struct stack_st_##type