spurious error if specs are given in wrong order

[jklmnn]

If the specs are given in the wrong order and are in different directories RecordFlux emits an error that it could not find the spec. E.g. if a.rflx depends on b.rflx and they're in different directories the following command works:

rflx check b/b.rflx a/a.rflx
Parsing b/b.rflx
Parsing a/a.rflx
Processing A
Processing B

Changing the order of the arguments will lead to an error even though the actual specs are correct and the dependencies are resolved:

rflx check a/a.rflx b/b.rflx
Parsing a/a.rflx
Parsing a/b.rflx
Parsing b/b.rflx
Processing A
Processing B
a/a.rflx:0:0: parser: error: Cannot read b.rflx

a/a.rflx:

with B;

package A is
end A;

b/b.rflx:

package B is
end B;

[treiher]

There are two issues with the current implementation:

1. A with clause is evaluated as soon as it is found, instead of waiting until all specifications, which are given as arguments, are parsed.
2. A specification is expected to be located in the same directory as the specification which contains the with clause, if the specification was not parsed before.

Given two specifications a/a.rflx and b/b.rflx, where a/a.rflx is importing C, the current implementation expects to have a file a/c.rflx. Even if both specifications would import C, (1.) would lead to parser error, if b/c.rflx, but no a/c.rflx would exist.

The better solution would be to parse all specification files, which are given as arguments, first, and do the evaluation of imported specifications afterwards. The directories of the given specification files could be considered as the include paths for the search of imported specifications.