-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inline cause compile error on MSVC 2013 or earlier #33
Comments
Sure. I'm in a time crunch this week (yes, even for an apparent 3line change in acism.h)
Given that only tiny static routines, defining inline as empty may work just as well. |
Change committed as shown; not tested. |
Thanks!
Den mån 25 maj 2020 22:14Mischa Sandberg <notifications@github.com> skrev:
… Change committed as shown; not tested.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#33 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGBGMUL7CGQSN7NPTWH2O53RTLGR7ANCNFSM4NITJV5A>
.
|
newer version Visual Studio(or c++ complier in VS2013) compiling fail since they already have inline keyword defined. |
Quick fix: insert |
Working on other (Unix ... SunOS, M1) platforms, the compilers
explicitly forbid
#defining compiler keywords. Can't say I blame them. Not that there
isn't a different workaround.
…On 23/05/2020, PerMagnusH ***@***.***> wrote:
Hi when compiling with MSVC (VS2013 or earlier) the inline keyword is not
supported. Is it possible for you to add a #define inline __inline for
MSVC?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
#33
--
Engineers think equations approximate reality.
Physicists think reality approximates the equations.
Mathematicians never make the connection.
|
Hi when compiling with MSVC (VS2013 or earlier) the inline keyword is not supported. Is it possible for you to add a #define inline __inline for MSVC?
The text was updated successfully, but these errors were encountered: