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
We are already using GNATCOLL and the files we parse are rather GNAT specific, so to be in line with other tools, we could just as well use a .gpr file as input instead of wildly scanning directories. This is especially important as specifying the object directory to parse also catches files from the saved_runs subdirectory, causing inconsistent behaviour by including data from earlier runs. Parsing the project files and selectively finding the associated .spark should be more user friendly.
The text was updated successfully, but these errors were encountered:
We are already using GNATCOLL and the files we parse are rather GNAT specific, so to be in line with other tools, we could just as well use a
.gpr
file as input instead of wildly scanning directories. This is especially important as specifying the object directory to parse also catches files from thesaved_runs
subdirectory, causing inconsistent behaviour by including data from earlier runs. Parsing the project files and selectively finding the associated.spark
should be more user friendly.The text was updated successfully, but these errors were encountered: