#522 Support intel-specific inquiry extension.

[hiker]

Adds the inquire-directory extension, to support Intel's specific arguments to inquire for directories (required for building Jules with Fab).

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.25%. Comparing base (743d453) to head (e69b8db).

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #523   +/-   ##
=======================================
  Coverage   92.25%   92.25%           
=======================================
  Files          89       89           
  Lines       13886    13891    +5     
=======================================
+ Hits        12810    12815    +5     
  Misses       1076     1076           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[hiker]

I have confirmed that with this change Fab can build Jules now. Ready for review.

[hiker]

FYI: Documentation from Intel:
https://www.intel.com/content/www/us/en/docs/fortran-compiler/developer-guide-reference/2024-2/obtain-file-information-inquire-statement.html

[arporter]

I really think Jules needs to be fixed! However, I have no real concerns about adding it as an extension.

[arporter]

All looks good, thanks Joerg.
Will proceed to merge.

[hiker]

I really think Jules needs to be fixed! However, I have no real concerns about adding it as an extension.

FWIW, that was my first idea as well, and I would have happily added a patch to a Jules source file to make Fab work. But it turns out that using inquiry for directories is non-standard. Using standard inquiry for an existing directory works with gnu, but not with intel. There were a suggested work around (test for directory/.), but that didn't work for my test either :( See https://fortran-lang.discourse.group/t/how-to-test-if-a-directory-exists/8731/11 with various solutions (usually involving C code).

I decided to give up, and extend fparser :)