Skip to content
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

Assume the highest supported compiler version when a new compiler is released #518

Open
rlebeau opened this issue Jan 13, 2024 · 0 comments
Labels
Element: Compiler/IDE Issues related to a particular Compiler and/or IDE Status: Reported Issue has been reported for review Type: Enhancement Issue is proposing a new feature/enhancement

Comments

@rlebeau
Copy link
Member

rlebeau commented Jan 13, 2024

In JEDI for example, when a new compiler version is released, jedi.inc defines various compiler directives (HAS_..., etc) from the highest supported compiler, thus easing compilation in new releases when non-breaking changes are not present.

Indy's IdCompilerDefines.inc does not define its HAS_... and ..._OR_ABOVE defines in new compiler versions, causing various compilation errors until IdCompilerDefines.inc is updated to recognize the new compilers. It should use a fallback, similar to how JEDI does.

@rlebeau rlebeau added Type: Enhancement Issue is proposing a new feature/enhancement Element: Compiler/IDE Issues related to a particular Compiler and/or IDE Status: Reported Issue has been reported for review labels Jan 13, 2024
@rlebeau rlebeau added this to the Indy 11 - Maintenance Release milestone Jan 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Element: Compiler/IDE Issues related to a particular Compiler and/or IDE Status: Reported Issue has been reported for review Type: Enhancement Issue is proposing a new feature/enhancement
Projects
None yet
Development

No branches or pull requests

1 participant