You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This works for C/C++ because the conditional compilation happens before parsing. In C3 there is conditional compilation, but after parsing, so not all modifications to the language would even work.
But what you ran into is an anomaly. It's due to development of the intentionally breaking 0.7.0 release. During 0.6.x, everything has been compatible even when something was deprecated. But 0.7 is a break with the 0.6.x series. After 0.7.0, the next breaking release is 0.8.0. And to put this into perspective: 0.9 will be followed by 1.0.
This means 0.7 is one of the last breaking versions (0.9 -> 1.0 should not break any language constructs, so only 0.6.x -> 0.7.0 and 0.7.x -> 0.8.0 and 0.8.x -> 0.9.0 will be allowed breaking the backwards compatibility)
For this reason, this period when 0.7 is built will be significantly less nice in following latest than usual. For 0.6.x it's generally been smooth sailing using latest otherwise.
Conditional compilation depending on the C3C compiler version.
In C++, the __cplusplus macro can be used to check the C++ standard and conditionally compile code
#if __cplusplus >= 201103L
// C++11 or newer
#else
// older C++-Version
#endif
What about implementing such a feature?
With such a feature my issue with the code could be handled.
Compilation broken since c3c 0.6.8 -> Error: 'Vector2' could not be found, did you spell it right? #2028
Just an idea.
The text was updated successfully, but these errors were encountered: