As for inline vs. __inline. The original code implies that most compilers
authorAndy Polyakov <appro@openssl.org>
Mon, 30 Jul 2007 11:42:08 +0000 (11:42 +0000)
committerAndy Polyakov <appro@openssl.org>
Mon, 30 Jul 2007 11:42:08 +0000 (11:42 +0000)
commit1891f5b395038901ab05c54e82367cea44a3f846
treea8bee948f8cd8e0558d9a55840db951d7cfdb515
parenta3963619f64377e5de7418c09bece61f8389b3fc
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...
crypto/stack/safestack.h