Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
`near` and `far` are reserved keywords in Visual C #1959
When defining an extension type containing two
This was a bit tricky to find the cause, but turns out
Of course, a workaround is to rename the attributes in Cython, for example to
So ideally, these reserved keywords should be translated to available names when generating the C source.
It should be enough to add both as non-C-safe identifiers here:
That will have an impact on existing code, though, which is annoying for something as non-standard as this... @robertwb, do you think we should add those? Do we need a transition phase here?
Well, technically Visual C/C++ (MSVC) does not have full c99 because it does not have things like VLAs which was required for c99 but became optional in c11. So MSVC is c98, c90, and c11 complient but not c99. (Sadly for c99 on MSVC it requires use of
And I hate clang for some reason... If I wanted clang I would be using linux to cross compile to Windows.