Files
mercury/tests/invalid_make_int/test_nested.int_err_exp
Zoltan Somogyi bdabaf5dc9 Make an error message more inclusive.
compiler/comp_unit_interface.m:
    When we cannot generate a .int0/.int/.int2 file because of file access
    issues, the reason is *usually* that we can't read a .int3 file.
    However, it is also possible that the reason is that we can't read
    a .int0 file, so include that possibility in the overall error message.
    (The "can't read this file" message, with the specifics of the file
    that couldn't be read, would have been printed earlier.)

tests/invalid_make_int/missing_parent_import.int_err_exp:
tests/invalid_make_int/sub_c.int_err_exp:
tests/invalid_make_int/test_nested.int_err_exp:
    Expect the updated error message.
2023-10-30 18:05:46 +11:00

12 lines
723 B
Plaintext

test_nested.m:013: Error: module `test_nested_helper_1' does not have a visible
test_nested.m:013: submodule named `test_nested_helper_4'.
test_nested.m:014: Error: module `test_nested_helper_1' does not have a visible
test_nested.m:014: submodule named `test_nested_helper_5'.
test_nested.m:017: In module `test_nested': error:
test_nested.m:017: the absence of an `:- import_module' or `:- use_module'
test_nested.m:017: declaration for `test_nested_helper_2' prevents access to
test_nested.m:017: the `:- use_module' declaration for its child module
test_nested.m:017: `test_nested_helper_2.test_nested_helper_6'.
Error reading .int3 and/or .int0 files.
`test_nested.int' and `test_nested.int2' not written.