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
When building a project with -gnat2022 then warnings about array obsolescent syntax are generated.
Coupled with gnatwe warnings as errors in gprbuild then the build fails.
I'm not sure of the best method to fix this issue? Personally, I would prefer upgrading the syntax to square brackets but that might break compatibility promises (not sure if they cover just hardware compatibility with the light runtime or if it is also intended to support older language versions). I have removed gnatwe from sparknacl gpr file in my codebase for now.
Note: Square brackets might cause problems with your ada language server such as breaking code formatting due to seeing incorrect code unless on a relatively new version (newer than the one bundled with the released gnat studio continuous release).
The text was updated successfully, but these errors were encountered:
I'll take a look when I have a sec. I think it will be worth making the transition to the new syntax if and when Ada2022 becomes the default mode in GNAT...
When building a project with -gnat2022 then warnings about array obsolescent syntax are generated.
Coupled with gnatwe warnings as errors in gprbuild then the build fails.
I'm not sure of the best method to fix this issue? Personally, I would prefer upgrading the syntax to square brackets but that might break compatibility promises (not sure if they cover just hardware compatibility with the light runtime or if it is also intended to support older language versions). I have removed gnatwe from sparknacl gpr file in my codebase for now.
Note: Square brackets might cause problems with your ada language server such as breaking code formatting due to seeing incorrect code unless on a relatively new version (newer than the one bundled with the released gnat studio continuous release).
The text was updated successfully, but these errors were encountered: